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.

Sign up for GitHub

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

Jump to bottom

Wildcard for unmatched key-value pairs #134

Closed
epage opened this issue Sep 2, 2022 · 1 comment
Closed

Wildcard for unmatched key-value pairs #134

epage opened this issue Sep 2, 2022 · 1 comment
Labels
A-snapbox Area: snapbox package breaking-change enhancement Improve the expected

Comments

@epage
Copy link
Contributor

epage commented Sep 2, 2022

#106 kicked off support for #92 but the match logic doesn't have a way to say "I don't care about any other key-value pairs".

How should this be represented?
@epage
Copy link
Contributor Author

epage commented Sep 6, 2022

If we support [..] within keys, then "[..]": "{...}" would mean "match all keys and all values for those keys".

With this route, we'd need a "match most specific first" approach to not have the wildcard consume all

@settings settings bot removed the A-snapbox label Aug 14, 2023
@epage epage added the A-snapbox Area: snapbox package label Aug 15, 2023
epage added a commit to epage/snapbox that referenced this issue May 23, 2024
@epage
feat(filter)!: Allow key wildcards
756c4de 
Fixes assert-rs#134
@epage epage closed this as completed in 4c1e2c0 May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-snapbox Area: snapbox package breaking-change enhancement Improve the expected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@epage