-
Notifications
You must be signed in to change notification settings - Fork 32
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
Validate custom column names #1013
Validate custom column names #1013
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1013 +/- ##
==========================================
+ Coverage 41.40% 42.15% +0.74%
==========================================
Files 430 430
Lines 32104 32115 +11
Branches 8040 8053 +13
==========================================
+ Hits 13293 13538 +245
+ Misses 18758 18524 -234
Partials 53 53
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Would be nice to add some CustomColumnBuilder
tests as well.
Ask and you shall receive The tests found a bug in Tab handling within the monaco editor (monaco was eating the tab). I have the fix for that behavior in this PR. I can split it out if you prefer |
1018abc
to
f249e57
Compare
Fixes #939
Does not validate that the names aren't duplicates of existing column names, only of existing custom columns. The API seems to allow custom columns that overwrite an existing column name. For example, table with coiumns
A, B, C
. Create a custom columnA=C
andB=A
. All of the columns will display columnC
. If you swap the order of the custom columns, thenB
will show the originalA
andA
will showC
.The API does not allow invalid custom column names (table column validation) or duplicate custom column names.