and maybe enabling a keyboard shortcut, e.g. Shift-Enter to manually run
This exists! Cmd+Enter on Macs, and it should be Ctrl+Enter on Windows, but I never checked. Please let me know if it doesn’t work for some reason. And I’ll add the tooltip.
Both in the VS Code extension and the Plaground, it would be great if settings persisted between sessions (this, combined with default Autorun, was a major pain point)
Some settings are already persisted in the playground on the website, but not Autorun, yet. You’re probably right that Autorun shouldn’t be the default.
In VS Code we’ll eventually support these through VS Code settings.
Also in the VS Code extension, the syntax highlighting is occasionally broken
Yes, there’s still a lot of work to do regarding the syntax highlighting and other quality-of-life features for VS Code (hovers, jump-to-definition, auto-formatting and so on).
I hope we’ll add some significant improvements in this area in the next few months.
Ah! Ctrl+Enter does work in the Playground. I was doing most of my development in VS Code—not sure if it’s also supposed to work there, but I don’t see it in the keybindings.json.
Re: settings persistence in Playground, do they also come along with the share links? The critical ones for me would be Sample Count and the Function Display Settings.
Share links are the only way settings persistence in the Playground works. But also for things such as Function Display Settings we eventually plan to support configuration through code and avoid adding too many UI settings (maybe even remove some).
This exists! Cmd+Enter on Macs, and it should be Ctrl+Enter on Windows, but I never checked. Please let me know if it doesn’t work for some reason. And I’ll add the tooltip.
Some settings are already persisted in the playground on the website, but not Autorun, yet. You’re probably right that Autorun shouldn’t be the default.
In VS Code we’ll eventually support these through VS Code settings.
Yes, there’s still a lot of work to do regarding the syntax highlighting and other quality-of-life features for VS Code (hovers, jump-to-definition, auto-formatting and so on).
I hope we’ll add some significant improvements in this area in the next few months.
Ah! Ctrl+Enter does work in the Playground. I was doing most of my development in VS Code—not sure if it’s also supposed to work there, but I don’t see it in the keybindings.json.
Re: settings persistence in Playground, do they also come along with the share links? The critical ones for me would be Sample Count and the Function Display Settings.
Looking forward to auto-formatting as well!
Oh right, shortcut for VS Code is missing, filed.
Share links are the only way settings persistence in the Playground works. But also for things such as Function Display Settings we eventually plan to support configuration through code and avoid adding too many UI settings (maybe even remove some).