🔵 We need your upvotes to move forward! 🎀 ⬆️ 🆙 ⬆️
yoavbls opened this issue · 0 comments
We need your votes on things we can't do ourselves because it depends on others
(e.g. VSCode and TypeScript teams on Microsoft, JetBrains, etc)
Please help us help everybody by voting in the links below 💙
1. Make types copyable
Solves #29
I made an issue + pull request for VSCode.
VSCode team may reject it because they already rejected requests for new style props before and promised to solve this in a more robust method, which didn't happen in the last 3 years.
So please:
⬆️ Upvote or comment here
2. Allow diagnostics messages to have markdown
Solves #15, #19, #3 and make us closer to solve: #11, #21, #26, #25
If VSCode allows it we could be able to move the formatting to a language server plugin which will allow us to:
- Control the order of the original error and the pretty one
- Hide the original error without losing it in the problems pane in VSCode or for other extensions like Error Lens
- Support more platforms more easily like Neovim, Visual Studio and maybe even JetBrains IDEs
⬆️ Upvote or comment here
3. JetBrains support
solves #11.
We saw a huge demand for support WebStorm and other JetBrains IDEs.
This ticket on YouTrack probably got JetBrains attention:
⬆️ Upvote or comment here
If you're a person from the relevant JetBrains team, please reach me out 💙