Feature/weos 1341 - As a developer I should be able to mark a fields as unique #117
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
added unique tag using gorm added unique test in projections
feature/WEOS-1355 - Add gorm tag for unique field on entity. Make getbyidentifiers method in projections.
added unique validation in domain service updated receiver functions sto use unique validator whee necessary
added integration test for unique constraint fixed batch create handler in module
feature/WEOS-1358 Add integration tests
feature/WEOS-1358 - Switched log level to debug for user generated unique error
…s-content-service into dev
akeemphilbert
approved these changes
Feb 23, 2022
akeemphilbert
requested changes
Feb 23, 2022
changed projections function name from GetByIdentifiers to GetByProperties
akeemphilbert
approved these changes
Feb 26, 2022
Aidan-E
approved these changes
Feb 28, 2022
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: