Design patterns·The named ways it goes wrong
the class exists only to call one method on another class and then disappears, and it has Manager in its name.
Poltergeist
Also calledpoltergeist class, gypsy class, transient controller
A short-lived object with no state and no real responsibility, existing only to invoke something else. It usually arrives from applying a layering or naming convention mechanically — every entity gets a manager, every action gets a controller — and the work it appears to do belongs elsewhere. Deleting it and calling the real thing directly is nearly always the whole refactoring.