You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my application I have a RestfulController that uses a no-domain class.
I cannot use the domain class directly because I need to do custom processing (field names and types, are different, ..). And I would like to avoid creating a fake domain object just for this.
But still I would like to use this plugin to document all my rest api.
So, do you think it would be a good idea to add functionality this plugin ?
Thanks
The text was updated successfully, but these errors were encountered:
Your idea is reasonable. But it seems that grails.rest.RestfulController is tightly bound to Grails domain classes, so I am not sure if grails.rest.RestfulController is the right choice for this usecase.
You can have a look to the method addDomainAndControllerClass in class ApiDocumentationService: It is the "heart" of this plugin - still quite a simple method that extracts all information from the Domain class and RestfulController. I think, it shouldn't be a problem to create an additional simplified version of this method for your more general approach. How should a Controller look like? How should the documentation look like?
Hi,
In my application I have a RestfulController that uses a no-domain class.
I cannot use the domain class directly because I need to do custom processing (field names and types, are different, ..). And I would like to avoid creating a fake domain object just for this.
But still I would like to use this plugin to document all my rest api.
So, do you think it would be a good idea to add functionality this plugin ?
Thanks
The text was updated successfully, but these errors were encountered: