TASK: Create database model for representing a Metadata Template #882
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
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…igration for unique name constraint
joshsadam
force-pushed
the
model/metdata-templates
branch
from
0028384 to
3c57fa7
Compare
This comment has been minimized.
This comment has been minimized.
deepsidhu85
previously approved these changes
Jan 8, 2025
ericenns
requested changes
Jan 9, 2025
…s and create schema file
Code Metrics Report
Code coverage of files in pull request scope (98.5%)
Reported by octocov |
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 does this PR do and why?
Describe in detail what your merge request does and why.
Created the database model (and tests) for representing a Metadata Template
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
NONE
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
NONE
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.