Foreign key visual identifier #66
Merged
Conversation
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
…main UI - Split single precision input into separate total/decimal digit fields for numeric types - Move precision/size configuration from three-dots menu to directly visible in table fields
- Size - Precision - Accuracy
|
LGTM |
…cy-section The Size, Precision, and Accuracy properties for table fields have been moved to the main side panel.
Feat: Added cardinality to subtypes
…t-subtype Removing cardinality start from subtypes relations
fix default data length setting when editing a field type
removed automatic uppercase and lowercase use based on default settings
…-warning fix typo in TableInfo which caused a warning
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.
Now the foreign keys have a more visual identifier with a default color that can be set by the user.