The JADE 2022 release meets tomorrow’s business demands.
We have had issues in the past with unnecessary creation of public methods, so we find it better if developers are defaulted to creating protected methods and must explicitly change it to public only when needed.
We use the Options>Preferences>Schema>Methods Access set to Protected and that works great for new methods.
However when using Right Click > Refactor > Extract Method command currently all methods are created as public.
Could the default for methods created with Refactor be set to protected as I imagine most use cases will be extracting to protected methods. Or if that isn't true at least make it configurable like it is for new methods in the preferences?
Roger Lammers
Good suggestion on inheriting, but for our use case I'm often extracting protected methods from public ones, so that wouldn't help in those scenarios.
I think the ideal compromise is for the option to be configurable in the preferences. That way we can set it to always create protected methods and existing developers who prefer creating public methods are unaffected by the change.
Inheriting sounds eminently sensible.
Maybe it would be better to 'inherit' the setting of the originating method?
I would prefer it created Public methods. Perhaps it should follow the option set in Preferences?