-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-12479] - Adding group-details endpoint #4959
base: main
Are you sure you want to change the base?
Changes from 4 commits
3621491
c5cd432
8fecf61
80d090f
6cfe7b3
ccdb29c
3ae2399
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This class needs to be updated a little to follow the newest patterns.
We're still refining our implementation of these so I'm not sure how clear this all is. See the Authentication Deep Dive for more info or feel free to send me a meeting invite if you want to sync on it. |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is optional depending on how deep you want to go with testing. But xUnit supports an attribute called We have a wrapper around it called BitMemberAutoDataAttribute which may provide some examples. |
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.
Why remove
groups
from the top-level route here?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.
The top level was removed since the new route would be
organizations/{id}/group-details
since group details isn't following/groups
. I believe the only way to override that would be to put a/
at the start of the route, but then you'd override any additional route pathing that was set up higher in the stack.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.
In that case I suggest leaving
groups
in the top-level route and usingdetails
at the method level, i.e.organizations/{id}/groups/details
. (We already do this for collection details.) My main concern is that all our controllers use a controller-level route, this would be an outlier that is easily missed. This also keeps all groups-related resources under thegroups
path which I think might be better REST design (although that might be arguable).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.
I see I specified
group-details
in the Jira ticket, that's my bad!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.
No worries. Easy fix. I'll move group back to the top and make this one details. I'll update the client code accordingly as well.