Membership: include business logic for patch
Open
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
PATCH: given item id, determine which membership to update: update membership on item or create a new one (also when it exists at root)
current logic actually happen in the client, where it decides which membership-id to modify (parent or current).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.