Skip to content
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

Fix bug: Ensure JSDoc type range is valid #27343

Merged
1 commit merged into from Oct 9, 2018
Merged

Fix bug: Ensure JSDoc type range is valid #27343

1 commit merged into from Oct 9, 2018

Conversation

ghost
Copy link

@ghost ghost commented Sep 25, 2018

Fixes a crash that occurred in updateTokenPositionsAndMarkElements when there was no type after @type as in /** @type */ and the document was then edited. (Similar to #26283)

This branch is based on #27162 and will be rebased after that is in.

@ghost ghost merged commit f6ca105 into master Oct 9, 2018
@ghost ghost deleted the editJsdocType branch October 9, 2018 00:09
ghost pushed a commit that referenced this pull request Oct 24, 2018
* Fix bug: Ensure JSDoc type range is valid

* Have scanJsDocToken scan keywords (#27162)

* Have scanJsDocToken scan keywords

* Update API

* Add 'no-unnecessary-type-assertion' tslint disables
mrcrane pushed a commit to mrcrane/TypeScript that referenced this pull request Jul 26, 2019
…t#28008)

* Fix bug: Ensure JSDoc type range is valid

* Have scanJsDocToken scan keywords (microsoft#27162)

* Have scanJsDocToken scan keywords

* Update API

* Add 'no-unnecessary-type-assertion' tslint disables
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant