- 15 11月, 2019 5 次提交
-
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
This reverts commit 544b0abf.
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
This reverts commit e24fefe0.
-
- 14 11月, 2019 35 次提交
-
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Benjamin Pasero 提交于
* update docs on fs provider for mtime * size is also needed
-
由 Benjamin Pasero 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Benjamin Pasero 提交于
-
由 Johannes Rieken 提交于
-
由 Christof Marti 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Matt Bierner 提交于
Some users are setting weird errors related to untitled TS files. In some of these cases (such as https://github.com/microsoft/TypeScript/issues/35091) we see a untitled file being sent to the tsserver without the `inMemoryResourcePrefix`. I can't figure out how to get into this state but am removing the gating that *could* perhaps cause use not to set `inMemoryResourcePrefix`. This gating targets TS 2.7 or older, which telemetry shows very, very few users are still enabling in their workspaces
-
由 Martin Aeschlimann 提交于
Added force-device-scale-factor to command line args
-
由 Benjamin Pasero 提交于
-
由 Martin Aeschlimann 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
由 Johannes Rieken 提交于
-
由 Matt Bierner 提交于
Fixes #84682 Also switches the use flexboxes to layout the parameter hints widget instead of absolute positioning
-
由 Miguel Solorio 提交于
-
由 Rob Lourens 提交于
-
由 Rob Lourens 提交于
-
由 Eric Amodio 提交于
AFAICT, the `-webkit-app-region: no-drag` of the resizer seems to only be honored for the first 4px. Any more and it doesn't eat the mouse event and creates a dead zone
-
由 Eric Amodio 提交于
-
由 Eric Amodio 提交于
-
由 Eric Amodio 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
Our code currently uses the `IConstructorSignature` types in a two main ways: - As argument types in functions that take a service constructor. - As return types or property types when we expose a service constructor in the API This first usage is not valid with strict function types. The reason is that the `IConstructorSignature` types takes a rest array of `...services: BrandedService[]` , while the concrete constructors you pass in use actual services. With strict function types, you cannot convert the concrete constructor type to an `IConstructorSignature` because this would drop important type information that the implementation needs. As an example ```ts class Foo { constructor(@ILogService service: ILogService) {} } registerFoo(Foo); // The type of `ctor` inlines `IConstructorSignature0` function registerFoo(ctor: { new(....serivces: BrandedService[]): Foo}) { // When registerFoo(Foo) is called, the implementation here would need to know that // ctor needs to be invoked with exactly one `ILogService`. However the type of `IConstructorSignature0` // does not express this. Strict function types therefore disallows this conversion } ``` To fix this, I have converted a few places were we were taking `IConstructorSignature` arguments so that they preserve the full type of the constructor. This fixed over half of our 900 strict function type errors. Unfortunatly I can not figure out a more elegant way to express this besides inlining the types However, even after this change, we still need to figure out how to deal with: - Places in the code where `IConstructorSignature` is exposed as a return type or object property - How to deal with all of our descriptor types (such as `SyncActionDescriptor`)
-
由 Pine Wu 提交于
-