Christian Flothmann
Christian Flothmann
I do not know anything about aaPanel, but in your screenshot it displays a warning that no `composer.json` file could be found. Maybe what aaPanel does in this case is...
I don't think this can be fixed easily. The YAML parser will replace the constant with its actual value at runtime, so the dumper will only be able to dump...
I think you should rather make it possible to attach this constraint not only to constraints, but also to getter methods like it is done for most of the core...
@Neirda24 Sorry, I misread your PR. However, looking at what you would like to achieve, wouldn'it be better to allow to pass a property path (rather than a method name)...
@Neirda24 Well, you could make that dependency optional and throw an exception if the constraint is configured with a property path while the component is not available. However, I don't...
@Neirda24 Afaik @rh389 needs to make the decision as he is the main maintainer of this bundle now.
Imo you should then also set the allowed types for this option to `string` and `callable`.
@sstok Using the term "root form" in the initial description was not quite right. In fact I see it to work for every (compound) form type that uses the `factory`...
The `@deprecated` annotation was not added by intent in core as only parts of the method are deprecated (just the feature to be able to use a filename instead of...
I still think that this isn't an issue you can resolve with static code analysis (you can hardly tell if the passed value is a filename or simply a YAML...