-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Issue with TypeScript definitions for selectTab #11193
Labels
Comments
DaSchTour
added a commit
to kpsdotcom/foundation-sites
that referenced
this issue
Apr 24, 2018
Can you please check if the changed definition file here #11199 fixes the problem |
@DaSchTour It looks like it does. Thanks! |
ncoden
added a commit
to ncoden/foundation-sites
that referenced
this issue
May 16, 2018
Foundation public methods does not all take a jQuery element as first parameter. They can actually take anything and the jQuery interface does not allow to know by the method definition to which plugin the method belong (and what are its arguments types). So the only solution seems to accept anything. See foundation#11199 (comment) Closes foundation#11193
14 tasks
ncoden
added a commit
that referenced
this issue
May 24, 2018
…-definition-11193 fix: fix Typescript jQuery foundation method definition #11193
ncoden
added a commit
to ncoden/foundation-sites
that referenced
this issue
Jun 16, 2018
…n-global-definition-11193 for v6.5.0 cac478c chore: move typescript definitions out of dist folders 5e540b7 fix: fix Typescript jQuery foundation method definition foundation#11193 Signed-off-by: Nicolas Coden <nicolas@ncoden.fr>
This was referenced Jun 16, 2018
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce this bug:
$("#matchGames").foundation("selectTab", "#result");
What should happen:
No TypeScript error –
elem
can be a string according to the docs.What happened instead:
TypeScript error:
Argument of type '"#result"' is not assignable to parameter of type 'JQuery<HTMLElement>'.
The problem is here:
... but changing that might not be ideal?
Browser(s) and Device(s) tested on:
n/a
Foundation Version(s) you are using:
6.4.3
Test case link:
n/a
The text was updated successfully, but these errors were encountered: