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
Moo 1.2 and earlier supported some finer-grained annotations, but as the configuration options grew, I started to need several annotations for even moderately simple cases, and it started to look polluted. Moo 1.3 uses a single annotation approach with multiple attributes that works well for complex cases, but is slightly more painful on the simplest cases.
It would be nice if Moo could support either approach, so a complex case could still be a single annotation with lots of attributes but a simple case could be met with single no-attribute annotation.
This is more work for Moo; it would have to recognize more configuration options, and it would need to validate that they don't conflict with one another, but it might make the experience of configuring Moo for a particular project more pleasing.
The text was updated successfully, but these errors were encountered:
Moo 1.2 and earlier supported some finer-grained annotations, but as the configuration options grew, I started to need several annotations for even moderately simple cases, and it started to look polluted. Moo 1.3 uses a single annotation approach with multiple attributes that works well for complex cases, but is slightly more painful on the simplest cases.
It would be nice if Moo could support either approach, so a complex case could still be a single annotation with lots of attributes but a simple case could be met with single no-attribute annotation.
This is more work for Moo; it would have to recognize more configuration options, and it would need to validate that they don't conflict with one another, but it might make the experience of configuring Moo for a particular project more pleasing.
The text was updated successfully, but these errors were encountered: