-
Notifications
You must be signed in to change notification settings - Fork 396
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
More TypeScript. Missing types or wrong usage? #3367
Comments
These are likely issues with the .d.ts file for ractive. I took a file from
|
I think I've got all of these resolved on edge once travis finishes doing its thing. |
Description:
I've some more questions on typescript. Either there are some missing types/signatures or I may be using it wrong:
Ractive.transitions
seems to be missing entirely in the typesRactive.WELCOME_MESSAGE
seems to be missing in types or is there another way to silence the welcome message`?Types for
EventPlugin
state, that thefire
callback takes one argument of typeEvent
but Examples at https://ractive.js.org/plugins/#writing_4 it's used like this:fire({ node: node, original: event })
which does not match the signature. Is the matching signature missing in the types or is it supposed to be used in another way?I've used
Ractive.defaults
to add some global helpers to all ractive instances, e.g. to use them in the templates like@.helper()
This used to work back in good old JS days:
But typescript says that
Ractive.defaults
does not accept custom properties. Is this missing in the TS types or are there new ways to add methods to all instances, primarily to use them in the templates.Versions affected:
1.3.14
The text was updated successfully, but these errors were encountered: