maxmustermann/TypeScript
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
TypeScript/tests/cases/fourslash/referencesForStringLiteralPropertyNames7.ts

17 lines
722 B
TypeScript
Raw Normal View History

Property assignments in Typescript (#26368) * Allow special property assignments in TS But only for functions and constant variable declarations initialised with functions. This specifically excludes class declarations and class expressions, which differs from Javascript. That's because Typescript supports `static` properties, which are equivalent to property assignments to a class. * Improve contextual typing predicate Don't think it's right yet, but probably closer? * More fixes. The code is still fantastically ugly, but everything works the way it should. Also update baselines, even where it is ill-advised. * Cleanup * Remove extra whitespace * Some kind of fix to isAnyDeclarationName It's not done yet. Specifically, in TS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I think I got them to be. (But not sure). In JS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I'm pretty sure ALL top-level assignments have been declaration sites for some time. This is incorrect, and probably means the predicate needs to be the same for both dialects. * Add fourslash and improve isAnyDeclarationName Now JS behaves the same as TS. * Cleanup from PR comments
2018-08-16 00:25:25 +02:00
/// <reference path='fourslash.ts'/>
// @Filename: foo.js
// @noEmit: true
// @allowJs: true
// @checkJs: true
Rename to use contextSpan
2019-06-13 21:25:02 +02:00
////var x = { [|"[|{| "isWriteAccess": true, "isDefinition": true, "contextRangeIndex": 0 |}someProperty|]": 0|] }
Support some late-bound special property assignments (#33220) * Support some late-bound special property assignments * Integrate PR feedback * PR feedback * Enable declaration on core tests * Specialize type of binary expression used for late binding, speculative fix to navigation bar, merge check and type for elem/property accesses * Add test showing current nav bar behavior (specifically the lack thereof)
2019-09-27 22:54:50 +02:00
////[|x["[|{| "isWriteAccess": true, "isDefinition": true, "contextRangeIndex": 2 |}someProperty|]"] = 3;|]
////[|x.[|{| "isWriteAccess": true, "isDefinition": true, "contextRangeIndex": 4 |}someProperty|] = 5;|]
Property assignments in Typescript (#26368) * Allow special property assignments in TS But only for functions and constant variable declarations initialised with functions. This specifically excludes class declarations and class expressions, which differs from Javascript. That's because Typescript supports `static` properties, which are equivalent to property assignments to a class. * Improve contextual typing predicate Don't think it's right yet, but probably closer? * More fixes. The code is still fantastically ugly, but everything works the way it should. Also update baselines, even where it is ill-advised. * Cleanup * Remove extra whitespace * Some kind of fix to isAnyDeclarationName It's not done yet. Specifically, in TS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I think I got them to be. (But not sure). In JS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I'm pretty sure ALL top-level assignments have been declaration sites for some time. This is incorrect, and probably means the predicate needs to be the same for both dialects. * Add fourslash and improve isAnyDeclarationName Now JS behaves the same as TS. * Cleanup from PR comments
2018-08-16 00:25:25 +02:00
Support some late-bound special property assignments (#33220) * Support some late-bound special property assignments * Integrate PR feedback * PR feedback * Enable declaration on core tests * Specialize type of binary expression used for late binding, speculative fix to navigation bar, merge check and type for elem/property accesses * Add test showing current nav bar behavior (specifically the lack thereof)
2019-09-27 22:54:50 +02:00
const [r0Def, r0, r1Def, r1, r2Def, r2] = test.ranges();
More Tests
2019-06-03 23:13:47 +02:00
const ranges = [r0, r1, r2];
Property assignments in Typescript (#26368) * Allow special property assignments in TS But only for functions and constant variable declarations initialised with functions. This specifically excludes class declarations and class expressions, which differs from Javascript. That's because Typescript supports `static` properties, which are equivalent to property assignments to a class. * Improve contextual typing predicate Don't think it's right yet, but probably closer? * More fixes. The code is still fantastically ugly, but everything works the way it should. Also update baselines, even where it is ill-advised. * Cleanup * Remove extra whitespace * Some kind of fix to isAnyDeclarationName It's not done yet. Specifically, in TS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I think I got them to be. (But not sure). In JS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I'm pretty sure ALL top-level assignments have been declaration sites for some time. This is incorrect, and probably means the predicate needs to be the same for both dialects. * Add fourslash and improve isAnyDeclarationName Now JS behaves the same as TS. * Cleanup from PR comments
2018-08-16 00:25:25 +02:00
verify.referenceGroups(r0, [{ definition: '(property) "someProperty": number', ranges }]);
verify.referenceGroups([r1, r2], [
More Tests
2019-06-03 23:13:47 +02:00
{ definition: '(property) "someProperty": number', ranges },
Property assignments in Typescript (#26368) * Allow special property assignments in TS But only for functions and constant variable declarations initialised with functions. This specifically excludes class declarations and class expressions, which differs from Javascript. That's because Typescript supports `static` properties, which are equivalent to property assignments to a class. * Improve contextual typing predicate Don't think it's right yet, but probably closer? * More fixes. The code is still fantastically ugly, but everything works the way it should. Also update baselines, even where it is ill-advised. * Cleanup * Remove extra whitespace * Some kind of fix to isAnyDeclarationName It's not done yet. Specifically, in TS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I think I got them to be. (But not sure). In JS: Special property assignments are supposed to be declaration sites (but not all top-level assignments), and I'm pretty sure ALL top-level assignments have been declaration sites for some time. This is incorrect, and probably means the predicate needs to be the same for both dialects. * Add fourslash and improve isAnyDeclarationName Now JS behaves the same as TS. * Cleanup from PR comments
2018-08-16 00:25:25 +02:00
]);
Reference in a new issue Copy permalink