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
I'd like to see the new globals from jasmine 3.4 added to the globals list, so that specifying env: jasmine in eslint includes globals like spyOnAllFunctions without having to add it manually to the .eslintrc.
I see the discussion in #82, and I'm not sure what the current status is -- is globals accepting PRs for adding globals to existing definitions, or is it already moving to separate plugins?
There exists a plugin today, eslint-plugin-jasmine, that is only a bundle of rules today. I'd be willing to make pull requests there to propose exporting a custom env, but if it exports the env "jasmine", will that be useable in .eslintrc? (I assume, perhaps, it would be env: "jasmine/jasmine" instead of just "jasmine").
Looking for input on where I should be making these changes...
The text was updated successfully, but these errors were encountered:
UziTech
added a commit
to UziTech/globals
that referenced
this issue
Aug 8, 2019
I'd like to see the new globals from jasmine 3.4 added to the globals list, so that specifying
env: jasmine
in eslint includes globals likespyOnAllFunctions
without having to add it manually to the .eslintrc.I see the discussion in #82, and I'm not sure what the current status is -- is globals accepting PRs for adding globals to existing definitions, or is it already moving to separate plugins?
There exists a plugin today, eslint-plugin-jasmine, that is only a bundle of rules today. I'd be willing to make pull requests there to propose exporting a custom env, but if it exports the env "jasmine", will that be useable in .eslintrc? (I assume, perhaps, it would be
env: "jasmine/jasmine"
instead of just "jasmine").Looking for input on where I should be making these changes...
The text was updated successfully, but these errors were encountered: