-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Wrong Typescript declared types #642
Comments
Hello, they're definitely outdated; Can you send a PR? 🙏 Also, I think it's missing rules set can contain a |
@Kikobeats what is the release cycle or when is the next version coming out? |
as soon as PR is merged, a new version is released |
it's been merged and it's still on 5.34.7 |
oh sorry; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
package.json
.Subject of the issue
The Typescript types are not correct.
Package like metascraper-image exports a function that returns an object.
i.e
However in the declaration file,
metascraper-*
packages exports a function that returns a function that returns an object which is not true.i.e
For more clarity, the expanded equivalent is:
I believe it should return
RuleSet
directly instead.Next, the "constructor" function accepts wrong types.
It should accept
RuleSet
and notRules
.If it were to accept
Rules
, the "constructor" should look like:instead of
htmlDom
fromCheckOptions
interface should also beinstead of
Otherwise it causes the error "This expression is not callable."
I can submit a PR but I'm not sure yet if this is intentional or if I'm missing something.
The text was updated successfully, but these errors were encountered: