-
Notifications
You must be signed in to change notification settings - Fork 1
Generalize /children endpoints to be usable outside of landing page #3, general rewrite/update #2 #6
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
Conversation
… general rewrite/update #2
gadomski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor copy-edits, otherwise makes sense to me.
Co-authored-by: Pete Gadomski <pete.gadomski@gmail.com>
|
This PR implements the hierarchical navigation concepts (specifically having /children accessible on any catalog/collection and not just the root) that were the core focus of my previous PR #4 While I understand this is an improved version, it effectively replaces PR #4. To preserve the history of this architectural pattern, could you please add me as a co-author on the merge commit? |
jsignell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me as well
Co-authored-by: Julia Signell <jsignell@gmail.com>
cc @jonhealy1
Related Issue(s):
Proposed Changes:
parentrelation typePR Checklist: