[Service SBS] Private service and repository members on Services #24614
MRodriguez08
started this conversation in
General
Replies: 1 comment 1 reply
-
thanks for bringing this up. I suppose the fields are private as we don't have an option to tell jhipster "this service should be extended" such that the generated class has protected fields only. When it comes to extending repositories you will need to mark the generated repositories with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello people! I'm a new jhipster developer and I really loved the power and architecture of this framework! I'm still learning all the internals and the de workflows (in particular sbs)
Have a doubt in regards of the Service and Repository Extension, part of the side by side approach.
Why are the services and repository members PRIVATE in the generated classes?? wouldn't be better to have them PROTECTED and be able to use them in the subclasses (ie: UserExtendedService), since they are injected by the super call in constructor.
Right now I have to re-define the services members on my subclass (ext) to be able to use it on some, let's say) overriden method I want to customize.
Pretty sure There's a reason,
Thanks in advance! great tool here!
Beta Was this translation helpful? Give feedback.
All reactions