We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to release log feature add fuzzy option to match commands was introduced in v13.9.0 Current type definition for match()is:
match()
match(match: string | ExtendedDocument<Ext, W, Ph>, options:any): ExtendedDocument<Ext, W, Ph>
That means that options is required param now, thus all my match, matchOne, etc... methods have errors.
options
match, matchOne, etc...
Looks like options param is optional (some pun intended), so we should have it this way:
options?:any vs options:any
I created PR to fix this and few typos along the way
The text was updated successfully, but these errors were encountered:
released as 13.9.2 thank you for the heads-up Ihor!
13.9.2
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
According to release log feature add fuzzy option to match commands was introduced in v13.9.0
Current type definition for
match()
is:That means that
options
is required param now, thus all mymatch, matchOne, etc...
methods have errors.Looks like
options
param is optional (some pun intended), so we should have it this way:I created PR to fix this and few typos along the way
The text was updated successfully, but these errors were encountered: