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
feat(explore): new datasets have autocomplete filters enabled if UX_BETA is set #15864
Conversation
5e0240e
to
16d03cd
Compare
Codecov Report
@@ Coverage Diff @@
## master #15864 +/- ##
==========================================
- Coverage 77.08% 76.84% -0.25%
==========================================
Files 984 984
Lines 51788 51801 +13
Branches 7037 7038 +1
==========================================
- Hits 39923 39807 -116
- Misses 11640 11769 +129
Partials 225 225
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/testenv up FEATURE_UX_BETA=true |
@kgabryje Ephemeral environment spinning up at http://34.213.99.235:8080. Credentials are |
/testenv up FEATURE_UX_BETA=true |
@kgabryje Ephemeral environment spinning up at http://54.244.217.223:8080. Credentials are |
405dc35
to
21a1317
Compare
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.
LGTM - one minor 🤔 but it shouldn't be blocking as this is behind a FF
if (isFeatureEnabled(FeatureFlag.UX_BETA)) { | ||
config.operator = OPERATOR_ENUM_TO_OPERATOR_TYPE[Operators.IN].operation; | ||
config.operatorId = Operators.IN; | ||
} |
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.
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.
good idea! it would be great to have the numeric slider in adhoc filter eventually when we redesign the entire component.
For temporal columns, i doubt users would use adhoc filter for it.
For numeric, we can use "=" or "<"? either way, the preselection is not gonna trigger any query, or adding additional clicks to selection, so the change is harmless. it really depends on what our best guess is without further data.
Ville's comment will be addressed in a follow up PR |
Ephemeral environment shutdown and build artifacts deleted. |
…ETA is set (apache#15864) * feat(explore): new datasets have autocomplete filters enabled if UX_BETA is set * Lint fix * Set autocomplete to True in example datasets * Use "IN" as a default operator in dnd filters * Default operator only if UX_BETA enabled
…ETA is set (apache#15864) * feat(explore): new datasets have autocomplete filters enabled if UX_BETA is set * Lint fix * Set autocomplete to True in example datasets * Use "IN" as a default operator in dnd filters * Default operator only if UX_BETA enabled
…ETA is set (apache#15864) * feat(explore): new datasets have autocomplete filters enabled if UX_BETA is set * Lint fix * Set autocomplete to True in example datasets * Use "IN" as a default operator in dnd filters * Default operator only if UX_BETA enabled
…ETA is set (apache#15864) * feat(explore): new datasets have autocomplete filters enabled if UX_BETA is set * Lint fix * Set autocomplete to True in example datasets * Use "IN" as a default operator in dnd filters * Default operator only if UX_BETA enabled
SUMMARY
If
UX_BETA
feature flag is set to True, all new datasets will have autocomplete filters enabled by default. The existing datasets will not be modified.The existing datasets have been set to use autocompleting feature regardless of the feature flag value.
Also, adhoc filters in drag and drop mode have "IN" selected as a if UX_BETA is enabled.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Screen.Recording.2021-07-23.at.13.37.34.mov
Screen.Recording.2021-07-26.at.12.32.25.mov
TESTING INSTRUCTIONS
UX_BETA
feature flagADDITIONAL INFORMATION
CC @junlincc @graceguo-supercat