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.

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

The TypeScript signature does not reflect the way the plugin works #134

Closed
NoriSte opened this issue May 13, 2020 · 1 comment · May be fixed by JoKacar/specter-desktop#15
Closed

The TypeScript signature does not reflect the way the plugin works #134

NoriSte opened this issue May 13, 2020 · 1 comment · May be fixed by JoKacar/specter-desktop#15
Labels

Comments

@NoriSte
Copy link
Owner

NoriSte commented May 13, 2020

The following code
Screenshot 2020-05-13 at 08 19 36
generates the following TS errors

Argument of type '(subject: any) => any' is not assignable to parameter of type '() => any'.
Argument of type '(subject: any) => boolean' is not assignable to parameter of type '() => boolean | Chainable<boolean> | Promise<boolean>'.
Argument of type '(subject: any) => boolean' is not assignable to parameter of type '() => boolean | Chainable<boolean> | Promise<boolean>'.
Argument of type '(subject: any) => any' is not assignable to parameter of type '() => any'.

that means that the Generics of the signature are wrong.

@NoriSte
Copy link
Owner Author

NoriSte commented May 13, 2020

🎉 This issue has been resolved in version 1.7.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant