A lot of our time is spent in the live editor. In addition to showing us built in filters and having auto complete, it would be cool to see the line numbers, highlighting syntax errors in the jinja editors in the workflow and in the context editor prior to testing the entire thing and showing us which line triggered the error.

In the context editor because all variables are filled out it would be nice to see traditional vscode features like breakpoints and variable information along with a line by line debugger so we can see what’s going on per line.

Underneath could be a debugger window that shows a better formatted output with only need to know info rather than the whole jinja script. The current output area is vague, and looks like orange spaghetti. It tells us there’s a syntax issue somewhere in the jinja but doesn’t tell us where and we have to go to the bottom of the thing to see there’s an extra bracket somewhere. Not too helpful.

But if all of this sounds like a pain in the tail feathers, maybe it would be easier to have rewst have a button that opens vscode and passes vscode the context in json. Assuming there’s jinja extensions and a debugger installed, the context could be used to set environmental variables and the user could then continue in their vscode environment.

If they have git setup, fancy features, autosave, hotkeys, and so forth that would make one of the barriers to rewst somewhat easier.

Working in online Notebooks with an AI window helping us code and a debugger slash results window gave me a lot of ideas for what rewst could also have.