Yes, the problem is that some things are required for (class loader service) or make sense (custom instantiator, short name provider) only for those "type properties".

I wanted to reflect that in the fluent API, so you e.g. cant omit the class loader service when obtaining a type property (while you don't need that when e.g. obtaining an int or String parameter). So maybe we can leave these separate but try to find a better name?

E.g. `classProperty()` or `typeProperty()`?