Is there a way to have states live in directories other than the directory of the base abstract class? #202
-
I'm trying to generate an extendable structure where I provide a set of "base" states for a given field, but I want to be able to later add more states (from other directories). This would allow, for example, to provide extendable packages that provide a set of already implemented states. Haven´t found any way of manually registering or adding extra available states for a given field. In the docs, it only mentions that the state classes should live in the same base state class directory if you want to use custom names (docs). But if I don't locate the concrete state classes in the same directory, I get some errors whenever the package wants to cast the class name string value to the corresponding state. Say I define the base abstract state class at
If I try to get the state mapping from the base state class, I get an empty collection:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Yeah that's not supported, concrete state implementations must live in the same directory as the abstract class. |
Beta Was this translation helpful? Give feedback.
-
Merged in 2.4.0 |
Beta Was this translation helpful? Give feedback.
Merged in 2.4.0