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
When most endpoints share a common structure (like headers or other parameters), it could be useful to have a parent Dto class from which inheriting all Dto classes.
No code change is require, but the following snippets could complement the documentation of the data mapping.
For instance in my case I have a common parameter customer-name that is present in the OAS in most endpoints.
Having some form of "advanced mapping guide" would be nice to have. In a client project, we're doing similar things, but I can't share that as public examples.
The design in indeed an ABC implementation to allow advanced logic in Python to be flexible in handling different scenarios.
Hello,
When most endpoints share a common structure (like headers or other parameters), it could be useful to have a parent Dto class from which inheriting all Dto classes.
No code change is require, but the following snippets could complement the documentation of the data mapping.
For instance in my case I have a common parameter
customer-name
that is present in the OAS in most endpoints.And then create the "child" classes simply as follow:
And I can go even further by adding class attributes that would list the ignored properties:
And simply add the list of ignored properties in the child class:
The text was updated successfully, but these errors were encountered: