Skip to content
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(filters): display operator into input text filter from Grid Presets #288

Merged

Conversation

ghiscoding
Copy link
Owner

  • a use case that we have with the text InputFilter is that if have a filter that includes an operator inside the search text (e.g.: ">=55") and we save the Grid State in Local Storage or anything else and then we reload them as Grid Presets, the operator won't be showing up (it would only show "55" while keeping the Operator hidden but still in play) that is because the FilterService is doing the split (this is an Operator and these are the SearchTerm) and the Grid State only keeps the split, so in that case this PR adds an extra step that if we're using the setValues() method, then we're probably using a Grid Preset or an UpdateFilters and we should display the operator as part of the final displayed search string inside the input value

- a use case that we have with the text InputFilter is that if have a filter that includes an operator inside the search text (e.g.: ">=55") and we save the Grid State in Local Storage or anything else and then we reload them as Grid Presets, the operator won't be showing up (it would only show "55" while keeping the Operator hidden but still in play) that is because the FilterService is doing the split (this is an Operator and these are the SearchTerm) and the Grid State only keeps the split, so in that case this PR adds an extra step that if we're using the `setValues()` method, then we're probably using a Grid Preset or an UpdateFilters and we should display the operator as part of the final displayed search string inside the input value
@codecov
Copy link

codecov bot commented Mar 17, 2021

Codecov Report

Merging #288 (3670ce1) into master (2d106d4) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##            master      #288   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          209       209           
  Lines        12436     12467   +31     
  Branches      4254      4269   +15     
=========================================
+ Hits         12436     12467   +31     
Impacted Files Coverage Δ
packages/common/src/filters/inputFilter.ts 100.00% <100.00%> (ø)
packages/common/src/services/filter.service.ts 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d106d4...3670ce1. Read the comment docs.

@ghiscoding ghiscoding merged commit 3fad4fe into master Mar 17, 2021
@ghiscoding ghiscoding deleted the feat/grid-presets-display-operator-in-search-string branch March 17, 2021 23:12
ghiscoding added a commit that referenced this pull request Mar 23, 2021
- rolling back this change since Aurelia-Slickgrid filter presets on Client Example was no longer working as expected
ghiscoding added a commit that referenced this pull request Mar 23, 2021
fix(filters): rollback a change made in PR #288 causing preset issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant