Fix type annotations range

[michalsnik]

This PR fixes ranges in typeAnnotation nodes.

Full discussion and description of the problem can be found here: vuejs/vue-cli#1672 (comment)

Essentially, because of not updated range of typeAnnotation - the rule space-infix-ops reported wrong nodes causing confusion among typescript users.

[codecov-io]

Codecov Report

Merging #31 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #31      +/-   ##
==========================================
+ Coverage   85.89%   85.92%   +0.02%     
==========================================
  Files          32       32              
  Lines        1879     1883       +4     
  Branches      486      488       +2     
==========================================
+ Hits         1614     1618       +4     
  Misses        180      180              
  Partials       85       85

Impacted Files	Coverage Δ
src/ast/nodes.ts	100% <ø> (ø)	⬆️
src/script/index.ts	84.4% <100%> (+0.34%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update da877ec...ca85b03. Read the comment docs.

[michalsnik]

I know there are many more possible types, but they are rather children of these top level types. And what we need here at this moment is just the top level type annotation on Identifier. Unless there will be introduced another eslint rule that will respect further cases of typeAnnotation or returnType. What do you think?

[mysticatea]

Thank you for this PR. However, I'd like to go another way.

This is a known issue which is described in README.md.

If you use typescript-eslint-parser, the location of original nodes can be wrong. Waiting for typescript-eslint-parser to support parseResult.visitorKeys.
https://github.com/mysticatea/vue-eslint-parser#parseroptionsparser

The root cause is typescript-eslint-parser doesn't support parseResult.visitorKeys. Therefore, vue-eslint-parser couldn't know that the AST that typescript-eslint-parser generated has some custom node types.

I'd like to add the parseResult.visitorKeys support to typescript-eslint-parser in order to fix this problem.

[michalsnik]

Alright, I wasn't aware of the visitorKeys. Would you like to proceed with this? I won't be able to tackle it in the next few weeks unfortunately.

[michalsnik]

I added visitorKeys to typescript-eslint-parser here: eslint/typescript-eslint-parser#516

So I'm going to close this PR and wait for the feedback there :) It indeed addresses the issue more thoroughly 👍