Allow duplicating event definitions with a limit of 0 #16251
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With #16035 we try to enforce a new default event limit, without breaking backwards compatibility. The validations are making an exemption if an existing event definition is being edited which doesn't have an event limit yet (limit of 0) Duplicating event definitions was done in the frontend, and then creating a new one. This makes it impossible to differentiate between copy and create in the backend. - Create a new `/events/definitions/{definitionId}/duplicate` endpoint. Which creates a copy without performing a validation. - Also correctly set the state for unscheduled event defintions. This got missed with #15558 Refs #16035
kingzacko1
approved these changes
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With #16035 we try to enforce a new default event limit, without breaking backwards compatibility.
The validations are making an exemption if an existing event definition is being edited which doesn't have an event limit yet (limit of 0)
Duplicating event definitions was done in the frontend, followed by creating a new one.
This makes it impossible to differentiate between copy and create in the backend.
Create a new
/events/definitions/{definitionId}/duplicateendpoint. Which creates a copy without performing a validation.Also correctly set the state for unscheduled event defintions. This got missed with Add enabled field to EventDefinitionDto #15558
Refs #16035