Update from main plugin#1
Open
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Use CompilerSet to set the makeprg using local/global settings
Added a link in the _Installation_ section of the README, to the Installation Wiki page.
Added a link to the installation wiki
Add 'gf' to '.tsx' files
ECMAScript numeric separator proposal is now on stage3 https://github.com/tc39/proposal-numeric-separator and will come to TypeScript at version 2.7. microsoft/TypeScript#20324 Example: ```typescript const i = 123_456; const x = 0x1fa_EF6; const f = 123_456.0_456; const f2 = 123_456.4_5e1_2; ```
allow typed return values. Fixes#131.
Binary and octal literals
Fix integer literal
unknown type is added since TypeScript 3. https://blogs.msdn.microsoft.com/typescript/2018/07/30/announcing-typescript-3-0/#the-unknown-type
Split StorageClass keywords from Identifiers
Highlight unknown as typescriptType
Fix code points notation in string literals
Add g:typescript_ignore_browser not to highlight browser things
added a small example of compiler options specification
Fix Typo: gackgroundPosition -> backgroundPosition
It was missing from the `typescriptLogicSymbols` class, where I think it belongs.
Adding ! as logical operator
See ":help group-name" in Vim's help menu. Function: function name (also: methods for classes) Keyword: any other keyword
Fix typescript func keyword
Now paired '<>' close like (),{}, and []. Eg: ```typescript const myFunction = < GenericA, GenericB, GenericC >(a: GenericA, b: GenericB, c:GenericC): GenericA =>{return a } ```…RICS Add closing '>' to containing groups
Compatibility with latest vim
The exclamation character is considered as a `typescriptLogicSymbols` when in a `!==`, which breaks some fonts due to the color change. With this line exchange, the exclamation is interpreted as it should be (`typescriptOpSymbols`)
Extend global objects definition with js and node keywords
fix: support all legal regex flags
exclamation character wrong group
Add support for new typescriptreact filetype
Fix wrong link in 'README.md' file
This version of neovim has the same typescript support as vim 8 patch-8.1.1486, so we should override it as well.
Override neovim 0.5.0 and up's typescript support
Add nullish coalescing operator (??) to syntax
This should unset any options the plugin sets but we were also unsetting options we weren't setting here.
Fix undo_ftplugin
Implements the suggestion posted in: #193 (comment) Which aligns the plugin with what other popular plugins that override bundled syntax files do. eg. - https://github.com/plasticboy/vim-markdown (uses `hi def link` on version 508 and above) - https://github.com/tpope/vim-markdown (uses `hi def link` unconditionally) This stops highlighting from getting obliterated when activating a colorscheme that uses `:hi clear` (which will reset highlights back to defaults), such as a Base16 theme: - https://github.com/chriskempson/base16-vim/blob/3be3cd82cd31acfcab9a41bad853d9c68d30478d/colors/base16-one-light.vim#L146 or Dracula: - https://github.com/dracula/vim/blob/b2cc39273abbb6b38a3d173d2a5d8c2d1c79fc19/colors/dracula.vim#L19-L24 and presumably others.
fix: prefer default links except on ancient Vim versions
I think it's time that people moved on to other ways of highlighting Typescript code.
Add "satisfies" to keywords
Remove status from typescriptMessage
This keyword is recognized as of TypeScript 5.2: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-2.html
Add `using` as a recognized keyword
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update