GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||
GeezerVison is showing github.com — Allow any key type as an index signature parameter type by weswigham · Pull Request #26797 · microsoft/TypeScript Conversation
|
|
TypeScript Bot (@typescript-bot) test this |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Heya Wesley Wigham (@weswigham), I've started to run the extended test suite on this PR at 2c47d31. You can monitor the build here. It should now contribute to this PR's status checks. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
(2) typescript 2.9 not allow symbol to be used as index. microsoft/TypeScript#1863. Current there is a PR open to address this issue microsoft/TypeScript#26797
|
Ryan Cavanaugh (@RyanCavanaugh) I see you marked this for TS 3.2. Is that still the plan? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
TypeScript Bot (@typescript-bot) pack this |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Heya Orta Therox (@orta), I've started to run the tarball bundle task on this PR at 05f63f6. You can monitor the build here. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Hey Orta Therox (@orta), I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Hello, I found this PR and I am looking forward to its release. A question about this PR. type NumStr = `${number}` type Obj = { [key: `${NumStr}`]: string } const obj: Obj = { "0xff": "", // OK "100e10": "", // OK "100": "", // NG, but why? } // Type '{ "0xff": string; "100e10": string; "100": string; }' is not assignable to type 'Obj'. // Object literal may only specify known properties, and '"100"' does not exist in type 'Obj'. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Could this support optional indexers? This seems to work with the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Wesley Wigham (@weswigham) What's the status of this? The PR is still open and has the "Backlog" milestone, yet on the roadmap it's marked as done and already part of |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
It's been superseded by #44512. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Intuitive != expected != actual behaviour when combining string and symbol keys Index signature parameter type should allow for enums Allow indexing with symbols
There was an error while loading. Please reload this page.