-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Association Relationship #1
Comments
My feeling is that, aside from the directed association between interfaces (representing a hateoas link), we should ignore general class-class relationships for API generation (maybe not for JSON-LD generation though). That's because I see a common use case being the import of a large E-R model like the core component library or some large system database model - and default behaviour to follow all those relationships might lead to messy API specs. I'm thinking it's better that the modeller deliberately changes simple relationships to aggregations or compositions and gets an output better aligned with design intent. |
@onthebreeze , simple Association Relationship is not listed in the current specification. Is this type of relationships going to be supported by the specification for API Serialisation or will be just ignored?
The text was updated successfully, but these errors were encountered: