|
|
|
|
|
by indentit
1643 days ago
|
|
Pretty sure you're the best thing to happen to ST since Will joined the team :) What's your test suite like? Whenever something is regressed in a dev build, do you try to cover it with tests? Or are the UI side of things not tested in an automated fashion? What are the plans for matching VSCode's useful features, like the one whereby all syntaxes can inject themselves into Markdown fenced code blocks etc? It'd be great to see some better SQL syntax highlighting support - I saw a community effort on the Packages repo aiming to address this. Will there be a way to switch "active" sql dialect? Or configure it per project? |
|
Thanks, that means a lot :)
> What's your test suite like? Whenever something is regressed in a dev build, do you try to cover it with tests? Or are the UI side of things not tested in an automated fashion?
The UI toolkit as a whole and platform integrations don't have tests, but the core parts like file encodings, data structures, syntax highlighting, etc. are pretty well tested using both integration, unit and manual fuzz tests. We also make heavy use of debug asserts and asan to catch bugs during development.
> like the one whereby all syntaxes can inject themselves into Markdown fenced code blocks etc?
I can't say when, but something like this is certainly on my radar. It seems like a clear incremental improvement on the existing syntax highlighting functionality.
> It'd be great to see some better SQL syntax highlighting support - I saw a community effort on the Packages repo aiming to address this. Will there be a way to switch "active" sql dialect? Or configure it per project?
This one is a lot more tricky as there are various tradeoffs to make. It's in my backlog of things that need to be discussed with other package repository contributors.