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

Make FilteredMap key matching case-insensitive #153

Closed
wants to merge 2 commits into from

Conversation

eager
Copy link

@eager eager commented Jan 27, 2020

Goal

FilteredMap is currently case-sensitive, making complete matching tedious. For example, to match the keys password, USER_PASSWORD, and adminPassword would require three separate filters, password, PASSWORD, and Password. Filtering becomes simpler, and less surprising, if matching is case-insensitive.

Changeset

Changed

FilteredMap#shouldFilterKey converts both the key and filter to lower case before matching.

Tests

FilteredMapTest has additional test cases.

Discussion

Alternative Approaches

None

Outstanding Questions

None

Linked issues

Fixes #152

Review

For the submitter, initial self-review:

  • Commented on code changes inline explain the reasoning behind the approach
  • Reviewed the test cases added for completeness and possible points for discussion
  • A changelog entry was added for the goal of this pull request
  • Check the scope of the changeset - is everything in the diff required for the pull request?
  • This pull request is ready for:
    • Initial review of the intended approach, not yet feature complete
    • Structural review of the classes, functions, and properties modified
    • Final review

For the pull request reviewer(s), this changeset has been reviewed for:

  • Consistency across platforms for structures or concepts added or modified
  • Consistency between the changeset and the goal stated above
  • Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
  • Usage friction - is the proposed change in usage cumbersome or complicated?
  • Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
  • Concurrency concerns - if components are accessed asynchronously, what issues will arise
  • Thoroughness of added tests and any missing edge cases
  • Idiomatic use of the language

@abigailbramble
Copy link

Hi @eager - thanks for the PR. We would be interested in making this configuration option capable of taking regexes. If you were interested in making a PR for this, we'd be happy to take a look.

@abigailbramble abigailbramble added the awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks. label Feb 5, 2020
@eager eager closed this Nov 11, 2023
@eager eager deleted the gh-152 branch November 11, 2023 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Request tab includes cookies
2 participants