Update Member entity to expose member state
What does this MR do and why?
In !66916 (merged), we added a state machine for GroupMembers, which since got moved to Member in !71257 (merged).
This MR exposes the state via the Members Entity, as member_state
. The value of this attribute is the human readable state for the Member record.
The MemberEntity
merges in the UserEntity
, here, which means state
is already exposed, but is actually the User state, not the member.
To avoid introducing a breaking change by modifying that, I opted to use member_state
.
How to set up and validate locally
- Hit the API endpoint for a group
curl --request GET \ --url http://127.0.0.1:3000/api/v4/groups/:group_id/members/all \ --header 'PRIVATE-TOKEN: <your token>' \
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Vijay Hawoldar