For very large APIs, a lot of unused code is generated, because the services have code to handle every request.
So, we'll always generate a function per service operation.
The function will get as parameters:
The HttpClient
The rootUrl
The (possibly optional) operation parameters
The optional http context
It will return the Observable as always.
The generated services are refactored to call those functions instead of having the code inline.
As such, no perceptible changes will be introduced to existing generations.
A new option, "services" (which defaults to true) will control whether services should be generated. Setting it to false will only generate the functions, which can be directly imported and used by the application.
For very large APIs, a lot of unused code is generated, because the services have code to handle every request. So, we'll always generate a function per service operation. The function will get as parameters:
It will return the Observable as always.
The generated services are refactored to call those functions instead of having the code inline.
As such, no perceptible changes will be introduced to existing generations.
A new option, "services" (which defaults to true) will control whether services should be generated. Setting it to false will only generate the functions, which can be directly imported and used by the application.