Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LINK-2163: Add has_user_editable_resources field to API #984

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

harriris-vincit
Copy link
Contributor

@harriris-vincit harriris-vincit commented Sep 12, 2024

Description

Adds a new field has_user_editable_resources to event, image, place, keyword and keywordset endpoints. This allows the front-end to check before a form is saved if the related data source allows users to edit the given resource like an event.

Closes

LINK-2163

@terovirtanen
Copy link
Contributor

LINKEDEVENTS-API branch is deployed to platta: https://linkedevents-pr984.api.dev.hel.ninja 🚀🚀🚀

@harriris-vincit harriris-vincit requested a review from a team September 12, 2024 11:33
@harriris-vincit harriris-vincit marked this pull request as ready for review September 12, 2024 11:34
events/serializers.py Outdated Show resolved Hide resolved
events/serializers.py Outdated Show resolved Hide resolved
Copy link

sonarcloud bot commented Sep 13, 2024

Copy link
Contributor

@tuomas777 tuomas777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 🐻

@harriris-vincit harriris-vincit changed the title LINK-2163: Add is_user_editable_resources field to API LINK-2163: Add has_user_editable_resources field to API Sep 13, 2024
@harriris-vincit harriris-vincit merged commit d802de2 into main Sep 13, 2024
15 of 17 checks passed
@harriris-vincit harriris-vincit deleted the feature/LINK-2163 branch September 13, 2024 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants