-
Notifications
You must be signed in to change notification settings - Fork 121
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: Apply filters follow up #6034
Conversation
JIRA: GDP-2938 risk: low
- when apply all at once config is used - fix inverted logic for attribute working selection JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
- and rename cancel to close JIRA: GDP-2938 risk: low
- and rename cancel to close JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
- hide apply button instead of diable it when no changes - fix reversed selector JIRA: GDP-2938 risk: low
- add reset all working filters command - fix depcruiser errors JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
- trigger filter context change event for workign state changes too - handle filter invalid state properly JIRA: GDP-2938 risk: low
- enableDashboardFiltersApplyModes JIRA: GDP-2938 risk: low
JIRA: GDP-2938 risk: low
extended-test --backstop |
"extended-test --backstop" started. Check the progress here. |
"changes": [ | ||
{ | ||
"packageName": "@gooddata/sdk-ui-all", | ||
"comment": "Support of new filter mode Apply all at once", |
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.
It should be clear that it's a Dashboard component feature
@@ -84,6 +96,7 @@ export function DraggableAttributeFilter({ | |||
> | |||
<FilterComponent | |||
filter={filterToUse} | |||
workingFilter={enableDashboardFiltersApplyModes ? workingFilterToUse : undefined} |
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.
Is this prop really required?
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.
After discussion on Slack we decided to deprecate this prop for now and remove it in the future phase 5 refactoring.
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.
We will pass workingFilterToUse into regular filter prop instead.
Which means the inner filter state will think those incoming working filters are applied. But we do not need to distinguish between applied and working state for now. And we prefer to keep filters component API simple.
Similar change should be done for DateFilter.
❌ "extended-test --backstop" finished with result failure. Check the results here. |
- we will remove them and use regular variants for sync working state instead - improve changelog message JIRA: GDP-2938 risk: low
e6fbd76
to
87a3d19
Compare
- not sure why TypeScript check is not catching this JIRA: GDP-2938 risk: low
extended-test --backstop |
"extended-test --backstop" started. Check the progress here. |
❌ "extended-test --backstop" finished with result failure. Check the results here. |
extended-test --integrated |
"extended-test --integrated" started. Check the progress here. |
✅ "extended-test --integrated" finished with result success. Check the results 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.
LGTM
fix(sdk-ui-dashboard): make working state update in attribute filter
feat(sdk-ui-dashboard): show working selection in filter button
fix(sdk-ui-dashboard): make working state update date filter
feat(sdk-ui-dashboard): remove apply from attribute filter
feat(sdk-ui-dashboard): remove apply from date filter
feat(sdk-ui-dashboard): remove attribute filter status bar
feat(sdk-ui-dashboard): add unapplied filters banner
feat(sdk-ui-dashboard): make reset btn reset working filters too
fix(sdk-ui): missing localization entry for close button
feat(sdk-ui-dashboard): support saved views in apply all at once
fix(sdk-ui-dashboard): responsivness in apply all at once mode
feat(sdk-ui-dashboard): make crossfiltering work properly
feat(sdk-ui-dashboard): hide new apply all filters behind FF
Important
Please, don't forget to run
rush change
for the commits that introduce new features or significant changes 🙏 This information is used to generate the change log.Run extended test by pull request comment
Commands can be triggered by posting a comment with specific text on the pull request. It is possible to trigger multiple commands simultaneously.
Explanation
--backstop
The command to run screen tests.--integrated
The command to run integrated tests against the live backend.--isolated
The command to run isolated tests against recordings.--record
The command to create new recordings for isolated tests.--filter
(Optional) A comma-separated list of test files to run. This parameter is valid only for the--integrated
,--isolated
, and--record
commands.Examples