Update: Take type annotations into account in space-infix-ops

[codepunkt]

Test fails and i have no clue how i'm supposed to add babel-eslint to the testing stack for single tests.
Advice is welcome!

(fixes #5211)

[eslintbot]

Thanks for the pull request, @gonsfx! I took a look to make sure it's ready for merging and found some changes are needed:

• Pull requests with code require an issue to be mentioned at the end of the commit summary, such as (fixes #1234). Please update the commit summary with an issue (file a new issue if one doesn't already exist).

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[mention-bot]

By analyzing the blame information on this pull request, we identified @gyandeeps, @vitorbal and @michaelficarra to be potential reviewers

[jquerybot]

Thank you for your pull request. It looks like this may be your first contribution to a jQuery Foundation project, if so we need you to sign our Contributor License Agreement (CLA).

📝 Please visit http://contribute.jquery.org/CLA/ to sign.

After you signed, the PR is checked again automatically after a minute. If there's still an issue, please reply here to let us know.

---

If you've already signed our CLA, it's possible your git author information doesn't match your CLA signature (both your name and email have to match), for more information, check the status of your CLA check.

[platinumazure]

One possible path forward:

1. Look at package.json in the root project directory and see if "babel-eslint" shows up as a devDependency.
2. If not, add it and run npm install.
3. Then see if you can change the parser using a RuleTester option.

FYI: I'm not 100% sure RuleTester lets you change the parser- it's the sort of thing plugin authors would need but core rule developers wouldn't, so I don't know if we ever did that.

[michaelficarra]

This doesn't seem to have anything to do with #226. Did you mean to open this PR against a different repo?

[codepunkt]

@michaelficarra Thanks. No clue what happened here, but i fixed it.

@platinumazure Thanks for your feedback!

I have babel-eslint installed as a devDependency but i wasn't sure if and how to set it using a RuleTester option.

Also, i'm not sure if this should be implemented in eslint at all - it could probably also be done in eslint-plugin-babel.

[nzakas]

@gonsfx you should be able to set parser for an individual test just like you do other options.

[alberto]

@gonsfx If you want to pull babel-eslint, you have to add it to our package.json devDependencies

To use it, add parser: "babel-eslint" to your test object.

[nzakas]

@gonsfx are you going to finish this up?

[nzakas]

Carried over to #6723.