Josh Pike

thanks for such a great library. I am looking for this lib to replace our natively implemented mudmap sketch views on both iOS and android, if you need a tester...

> the decorator in typescript is not the same as ECMA spec What popular JS-only frameworks is using decorators according to the ECMA spec? Typescript is immensely popular nowadays, why...

Just read more on the TS side, looks like the new decorators won't land until TS 5.0 https://github.com/microsoft/TypeScript/issues/51362

https://github.com/tc39/proposal-decorators/issues/47#issuecomment-1094077700 https://github.com/microsoft/vscode/blob/33040b9696aa918784c818c5d375ec4a4c1f8e85/src/vs/code/electron-main/auth.ts#L67 This is where there's a good argument for proceeding with how decorators are defined right now. Parameter decorators are heavily used in frameworks like Angular, and also heavily...

as mentioned in #4049, I think there should be a stopgap solution that allows such an important rule to be able to be used. The bare minimum being parsing @decorator...

looks like this can be closed due to #4252

I've recently started running into the issue, as our codebase starts to acquire more dependencies. It's intermittent and unpredictable. Sometimes I get a passing test, sometimes it fails the moment...

this is a super important one, I'd even suggest putting it in the recommended set. It's super dangerous to allow people to accidentally reference a non-literal key due to it...

This is much preferred. As you can see I have quite a heavy config file here: https://github.com/rome/tools/discussions/3774 And the only way to try and track them is these issues https://github.com/rome/tools/issues/3966...

Bonus points if you have a GitHub action that runs on issue creation, and does a lookup of the title in the spreadsheet for easier linkage/reference