* Update LKG
* Add @types/node version bump
* Small paatches/casts to be compatible with latest node
* Accept API baseline update
* Make internal NodeBuffer compatable with latest Buffer
* Why do we even have an internal buffer type
* Sync up internal buffer type better
* Fix lint
* Readd mroe missing Buffer methods
* Bind a jsdoc enum as SymbolFlags.TypeAlias and not SymbolFlags.Enum
* Actually include an @enum tag as a declaration
* Add enum tag refs into a couple more syntax kind lists
* accept symbol baseline update
* Decrement line ends if they end with a carriage return.
* Changed handling of newlines and inlined regex operation.
* fixed misname of hintSpan
* added tests
* revert inline of regex match and use getLineEndOfPosition
* fixed lint error and changed a silly thing in tests
* Property assignment uses parent type annotation
First draft, will write full explanation later.
Also makes sure that jsdoc is ignored in TS. It was not before.
* Update baselines
* Strip more kinds of timestamps and versions from dockerfile output, rewrite office-ui-fabric dockerfile to use new lerna build system
* Add another filter for just output
* Update user baselines (#23)
* Update user baselines (#24)
* Strip only maybe-present timestamps
* More lenient timestamp filter
* Update user baselines (#25)
* Simplify and enhance vscode dockerfile to use nightly ts in ts extension, too
* Update user baselines (#26)
* Update user baselines (#27)
* Fix type keyword completions
1. In functions, type keywords were omitted.
2. In All context, no keywords were omitted.
(1) fixes#28737
(2) removes 17 keywords that should not be suggested, even at the
toplevel of a typescript file:
* private
* protected
* public
* static
* abstract
* as
* constructor
* get
* infer
* is
* namespace
* require
* set
* type
* from
* global
* of
I don't know whether we have a bug tracking this or not.
* Change keyword filter in filterGlobalCompletion
Instead of changing FunctionLikeBodyKeywords
* Add more tests cases
* Make type-only completions after < more common
Because isPossiblyTypeArgumentPosition doesn't give false positives now
that it uses type information.
