6 Commits (2869acf63b49539a4d9b4075fa5c566a3835e197)

Author	SHA1	Message	Date
ulferts	f18e484e97	add spec ensuring roles to exist on membership creation via api	4 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	e003ad0af7	turn scope and label unwritable	5 years ago
ulferts	48988dfeb8	add membership delete to api	6 years ago
ulferts	4cb76b5d37	add membership update to api	6 years ago
ulferts	a93ecca5a8	Feature/members api show (#7308) ... * basic members collection response * complete member index end point * document versions#index * remove user association from members There is already a more generic principals association. Having both causes confusion and leads to duplicate loading of models * linting * remove disabled test * add members#show api end point * add project and principal to member representer * replace member.user reference with principal * use principal reference in project members association * modernize roles api * complete member representer rendering * replace remnants of user association * add member schema api endpoint * have dedicated available projects end point for versions * linting * limit roles to assignable ones in schema * rename member to membership in api * remove remnants of user in member * spec fixes * use available_projects endpoint in versions board * add eager loading to memberships#index * members create form api endpoint * ensure role exists for default assignment * extract switch for users/groups to work_packages representer * document membership create form * add l10n expected in specs * strengthen the usage of a delete base service * use base class for set attributes service * fix alias in service * add create endpoint to members api * document members create endpoint * linting * adapt to altered service signature * use default endpoint for wp#get * use CF infused representer [ci skip]	6 years ago