You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accepting library-specific globals is a slippery slope of supporting all sorts of lesser-used libraries. Instead of trying to define which libraries are "popular enough" to justify inclusion, we're reserving new environment settings for true environments.
The GreenSock library might consider exporting a single variable on the global scope and using that as a namespace for its API. I only suggest changing the source code (instead of JSHint) in this case because the change would do more than address this specific problem (making linting configuration easier to manage). It's generally considered a best practice because it minimizes risk of collisions and it requires consuming code to be easier to follow (the origin of every method is communicated each time it is accessed).
Hi I'm currently working with GreenSock-JS (https://github.com/greensock/GreenSock-JS) and they have a bunch of globals (http://greensock.com/forums/topic/11369-gsap-globals-for-jshint/)
I wish I could just write
GSAP: true
The text was updated successfully, but these errors were encountered: