Skip to content

Issues: SimoneGianni/tsMatchers

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

11 Open 8 Closed
11 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Extend fluent syntax to other cases
#28 opened Sep 17, 2023 by SimoneGianni
Containers do not compose correctly on and.not.string
#27 opened Sep 17, 2023 by SimoneGianni
@SimoneGianni
Object matching, accepting matcher<any> hinders type safety
#24 opened Sep 2, 2022 by SimoneGianni
Add "oneOf" and similar
#23 opened Sep 1, 2022 by SimoneGianni
Wherever a number is expected, provide also a matcher based version
#22 opened Sep 1, 2022 by SimoneGianni
Better coordination between array and object matching
#21 opened Sep 1, 2022 by SimoneGianni
2
Make array equal (and matching) propagate to sub arrays as object does
#20 opened Aug 26, 2022 by SimoneGianni
@SimoneGianni
1
Improve object.matching error report
#18 opened Aug 23, 2022 by SimoneGianni
check with explicit type signature gives error on is.object.matching with a partial object
#17 opened Aug 19, 2022 by SimoneGianni
@SimoneGianni
4
Make the matcher interface empty
#15 opened Aug 17, 2022 by SimoneGianni
2
Offer polluting import
#14 opened Aug 17, 2022 by SimoneGianni
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.