-
Notifications
You must be signed in to change notification settings - Fork 0
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: expose array-like methods for searching data #4
Conversation
3356bb9
to
2464c38
Compare
cityData.name, | ||
cityData.province, |
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.
The data was manipulated to make the specific implementation of text search easier. But with that gone, I think it makes sense to expose these as-is.
Instead of limiting an end-user to a string search, enable `predicate` functions to `find` and `filter` values. BREAKING CHANGE: exposed api changed from string search to predicate methods
Co-authored-by: forstermatth <matt@autovance.com>
@@ -1,13 +1,12 @@ | |||
{ | |||
"name": "canadian-city-timezones", | |||
"version": "1.0.0", | |||
"version": "2.0.0", |
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.
If semver has been set up, do we need to change this?
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.
Not at all! Could even make it 0.0.0
or something.
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Instead of limiting an end-user to a string search, enable
predicate
functions tofind
andfilter
values.BREAKING CHANGE: exposed api changed from string search to predicate methods