Skip to content

Edit content via API

Alex requested to merge content-patch-api into master

What does this MR do?

New API endpoint PATCH /content/{id} for changing a content entry. The frontend is not yet written in vue, but changed to use the new endpoint.

How confident are you it won't break things if deployed?

very sure

Links to related issues

How to test

  1. Checkout branch locally
  2. Login as userorga
  3. Open the content list from the administration menu
  4. Choose an entry
  5. Change it and save

Screenshots (if applicable)

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
  • added an entry to CHANGELOG.md
  • added a short text in the release notes to /release-notes/YYYY-MM.md
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Merge request reports