4 ms·
>Thankfully they’re actively working to address that now. Where? The response I saw on GitHub issues (to the few people who considered it worthwhile to be voca
by kuramitropolis 4y ago
>Thankfully they’re actively working to address that now.
Where? The response I saw on GitHub issues (to the few people who considered it worthwhile to be vocal about the issue) was literally (well, paraphrased): "yeah we did this wrong but we're sticking to it anyway" (because of MS-internal org inertia I assume, something that the TS devs surely have to account for but it's hidden from us as an "open source" downstream)
- eyelidlessness 4y agoI’m going to bed but don’t want to leave this unanswered before I lose track of it. They’re working on it as part of the next major release and you can see that in the roadmap they’ve posted for it.