Wrong method signature when building REST implementation class using spec
When using the REST API classes for building services on a spec-first approach, the implementation class methods are usually built this format:
ClassMethod <method-name>(body As %DynamicObject) As %Stream.Object
But sometimes it keeps building the endpoint implementation method like this:
ClassMethod <method-name>(body As %Stream.Object) As %DynamicObject
It has been a problem because the rest of my implementation rely on the fact that the "body" object is a DynamicObject.
The REST spec is exactly the same for all endpoints, but this last it built keeps presenting this problem.
Someone has experienced the same issue?