Simplify blog example TypeRegistry

[spawnia]

No description provided.

[shmax]

Can I ask what the motivation was to get rid of the Types helper? Personally, I kind of like the old pattern; I could right-click something like user and choose "Find usages" in my IDE to quickly see where it's being used (and possibly more importantly, you would get intellisense action when filling out a type field) . I suppose you can technically do the same thing with the class name, but you will get cross-pollution from the class itself, static usages, and so on.

[spawnia]

[shmax]

Okay, so you lose about a hundred lines of code, but you also lose some handy tooling. If your goal is just to drop lines of code, you could always tighten up Types.php. I use a similar pattern in my own code, and my Types.php looks like this:

    public static function action() : callable { return static::get(ActionType::class);}
    public static function actionSort() : callable { return static::get(ActionSortType::class);}
    public static function actions() : callable { return static::get(ActionsType::class);}
    public static function appraisal() : callable { return static::get(AppraisalType::class);}
    public static function appraisalSet() : callable { return static::get(AppraisalSetType::class);}