thanks @ssmusoke for the suggestions
I respect yr thoughts and I totally understood what you are trying to portray !
But my point is if in case any user/developer who is trying to develop or generate a webapp, most probably he/she would try to make a rest call (according to their needs). So, in order to make rest calls through the webapp, they must know how to use the openmrsRest module which is present in the ui-commons library. If he/she doesn't even make efforts to just learn how to use openmrsRest module, then they may have to go through a long process of making rest calls by themselves (which would increase their learning curve again)
So, what I am doing here is, except few components which are used from the uicommons library, I am developing new components with Angular best practices which will use openmrsRest module for rest calls (the only openmrs specific approach they need to learn). So, they don't have to bother much about the logic behind the component and they should just have a brief idea about how rest module works.
And you are right for the components which are used from the uicommons library that they need an openmrs specific approach to be implemented. But, integrating it in the generator will enable them (users) to use those components without pain (as @dkayiwa has already mentioned in the previous comment) because they just have to make the html tag of the component name they want to use and then they can focus on whatever they want to program in that webapp ( as I don't think that anybody would use the openmrs owa generator to generate webapps for purposes other than to be used at openmrs )
or is it the thing that this generator is to be used for non - openmrs projects also ??
if this is the thing, then I guess my perception was wrong for this project !!