matrei commented on PR #15289: URL: https://github.com/apache/grails-core/pull/15289#issuecomment-3801250331
> > > Since add-field could also be useful, I think we should have add-field for fields and add-property for properties. > > > > > > @codeconsole What is the use case for adding a field to a domain class, and does that use case warrant a shell command? > > @matrei well, it's kind of a freebie due to inheritance. The original premise behind this PR was to slowly introduce codegen capabilities to where you could build a workable demo with cli commands. I've had use cases for static fields in my domain objects. > > I suppose I am indifferent. Adding properties is what is most important. Should we get rid of add-field altogether? @codeconsole My preference would be to remove `add-field` as it might make things more complicated for a user who has to think/remember which one to pick. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
