feat: add enum values to db specific configs#2420
Merged
Merged
Conversation
Pull Request Test Coverage Report for Build 15990500689Details
💛 - Coveralls |
aaqilniz
force-pushed
the
feat/enum-value
branch
7 times, most recently
from
June 30, 2025 10:19
24bea53 to
5b729e0
Compare
Signed-off-by: Muhammad Aaqil <aaqilcs102@gmail.com>
samarpanB
approved these changes
Aug 15, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Add values for enum types in the db-specific options in model files.
Checklist
npm testpasses on your machine