Adapt fields in profile rest controller to
What does this MR do?
This adapts the names of the fields of the profile rest controller to the rules discussed in #511. Additionally, this removes a few unused fields to avoid breaking changes in the future, if the endpoint is extended (as discussed in the original MR !880 (merged)).
How confident are you it won't break things if deployed?
Except my WIP MR for the app this is not used anywhere and not yet deployed to production, thus this breaking change should not break anything.
Links to related issues
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s))