Skip to content

New API endpoint for creating content entries

Alex requested to merge adding-content-rest into master

Preparation for a part of #401

What does this MR do?

Adds an API endpoint for adding content entries and makes the corresponding form use that endpoint. After this, the content form can be refactored to vue and we can get rid of jquery-tinymce.

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 orga
  3. Select "Inhalte bearbeiten" in the admin menu
  4. Click the button to add an entry
  5. Type something and submit the form
  6. Check in the table that the entry exists

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
  • set the "API change" label if changes in the API are not backward compatible
  • 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.
Edited by Alex

Merge request reports