You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have a rule that implements ConfigurableRectorInterface the assumption is that you must use the rule with configuration options. So when documenting the rule, if you do the following it will fail when trying to generate documentation.
This isn't reflective of the fact you can use a configurable rule without specific configuration applied via the config, relying on no configuration or provide an empty array as the configuration. This also generates an error.
Solution
To fix this, I propose that the validation for configurable rules must have at least one ConfiguredCodeSample provided but does not block the use of additional CodeSample being provided when a rule implements ConfigurableRectorInterface.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently if you have a rule that implements
ConfigurableRectorInterface
the assumption is that you must use the rule with configuration options. So when documenting the rule, if you do the following it will fail when trying to generate documentation.Equally if you try to document a rule with an empty array it fails.
This isn't reflective of the fact you can use a configurable rule without specific configuration applied via the config, relying on no configuration or provide an empty array as the configuration. This also generates an error.
Solution
To fix this, I propose that the validation for configurable rules must have at least one ConfiguredCodeSample provided but does not block the use of additional CodeSample being provided when a rule implements
ConfigurableRectorInterface
.Beta Was this translation helpful? Give feedback.
All reactions