[DATABRICKS-5] PLU-600: add frontend support for databricks dynamic actions#1530
[DATABRICKS-5] PLU-600: add frontend support for databricks dynamic actions#1530pregnantboy wants to merge 1 commit intodatabricks/4-create-rowfrom
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8cac423 to
dae7518
Compare
189d3bc to
f94b3fa
Compare
382be49 to
735d13a
Compare
f94b3fa to
6ee411e
Compare
735d13a to
4440c19
Compare
6ee411e to
41da125
Compare
kevinkim-ogp
left a comment
There was a problem hiding this comment.
two small nits, other than that lgtm tested and works 🧱
41da125 to
a3de2ea
Compare
4440c19 to
14cd673
Compare
| if (!/^[a-zA-Z0-9_]+$/.test(value)) { | ||
| return 'Only alphanumeric characters and underscores are allowed' | ||
| } |
There was a problem hiding this comment.
Validation regex doesn't match user-facing description. The regex /^[a-zA-Z0-9_]+$/ allows both uppercase AND lowercase letters, but line 81 tells users "Only lowercase letters, numbers and underscores allowed."
// Current regex allows uppercase:
if (!/^[a-zA-Z0-9_]+$/.test(value)) {
// Should be lowercase only:
if (!/^[a-z0-9_]+$/.test(value)) {Users will successfully create tables with uppercase letters, which may fail in Databricks if it requires lowercase names.
Spotted by Graphite
Is this helpful? React 👍 or 👎 to let us know.
Add dynamic action GraphQL mutation, refactor AddNewOptionModal to be config-driven with validation support, add databricks create-table and create-column cases, support inline validation on SingleSelect, and update collaborator restrictions to use addNewId-based checks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
a3de2ea to
775b175
Compare
14cd673 to
4e8abbc
Compare

Add dynamic action support and validation for dropdown options
Add dynamic action GraphQL mutation for creating Databricks tables and columns. Refactor AddNewOptionModal to use configuration-driven approach with validation support for different dropdown types. Implement inline validation for SingleSelect components and update collaborator permission checks to use addNewId-based restrictions instead of field-based ones.
DYNAMIC_ACTIONGraphQL mutation for handling dynamic dropdown actionsADD_NEW_OPTION_CONFIGSwith validation functionsdatabricks-createTableanddatabricks-createTableColumnin create new option flowCOLLABORATOR_RESTRICTED_ADDNEW_IDSinstead of field labels