-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CORE-368] Validate table rename #5272
Conversation
format: { | ||
pattern: '^(?!sys_)[a-z0-9_.-]*', | ||
flags: 'i', | ||
message: "Table name may only contain alphanumeric characters, underscores, dashes, and periods and cannot start with 'sys_'.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
table names cannot contain periods; they can start with sys_. Check the logic in Rawls as the source of truth for validation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than David's comment on formatting, looks good to me!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran it locally, works well!
Jira Ticket: https://broadworkbench.atlassian.net/browse/CORE-368
Validates table name before allowing rename.
Note: compare to EntityUploader.js - the logic was copied from there but there appears to be some extra validation coming from the datatable provider. Does that need to be included in renaming as well?
Summary of changes:
What
Why
Testing strategy