Skip to content
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

Extended related_topics Object to Optionally Include Reverse Relationships #40

Conversation

GeorgDangl
Copy link
Member

When asking for a topics relations, a query parameter can be used to include inverse relationships in the result. Additionally, the object's schema was flattened to be a list of strings (guids) instead of a list of objects since the only property in the object was the guid.

…lated topics and flattened array of related topics to string array; Flattened also arrays in PUT and PATCH schemas; Updated Readme to reflect these changes and added query parameter "IncludeInverse" to section 4.7.1 with example
@GeorgDangl
Copy link
Member Author

GeorgDangl commented Jun 14, 2016

Change documentation to explicitly state that topic relationships are always inverse / two sided
-> Creating a relation on Issue A with Issue B also creates a relation on Issue B with Issue A
Should documentat that this results in both topics being changed (modified date, ETag etc.)

Must also be covered in the Xml specification

Will be further discusses in a telecon

@GeorgDangl
Copy link
Member Author

As per todays telecon, this needs to be discussed further after the holiday season, so it's being left open for now.

@GeorgDangl GeorgDangl closed this Sep 26, 2016
@GeorgDangl GeorgDangl deleted the feature/relatedTopicsIncludeInverse branch February 1, 2021 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant