vscode-python VS quokka

help get this supported in vscode by liking the issue here: https://github.com/microsoft/vscode-python/issues/24916

The issue involved preventing test coverage from running a second time if it had already failed. I located the GitHub Actions workflow file and found the step responsible for running test coverage. By using the needs argument, I made the step depend on the earlier test steps to be completed. After updating the workflow and creating a pull request, I was happy to see it accepted and merged.

VS Code Python

The main contribution I worked on was for the vscode-python extension. The issue involved removing redundant JSDoc comments that TypeScript can already infer. Some of the comments were a repeat of what was can be understood from the typescript code, which meant they would need to be updated every time the code changed. The idea was to get rid of those types of comments but keep parts that added useful context.

Ah, Chrome and slow spinners.

Python tests were taking ages on VSCode due to an SVG spinner:

https://bugs.chromium.org/p/chromium/issues/detail?id=103626...

https://github.com/microsoft/vscode-python/issues/9216

It seems to be a problem caused by the new version of the Python extension. Here is a GitHub link for you to follow up.

For the python extension, please file your issue here: https://github.com/microsoft/vscode-python/issues

There seems to be a focus on feature velocity, and as the big parts start to stabilize (language server stuff, refactoring, extension framework, general UI/UX expectations), I hope we'll see some more attention paid to the default experience. But changing defaults in an ecosystem where users embrace configurability is tough, see the pythonPath fiasco, so I don't know the way forward. Core dev Brett Cannon seems to support the opinionated path for the VSCode Python experience going forward, so we'll see where that takes us.

I filed a GitHub report, you can always follow up.

You can try this implementation out in a REPL or Quokka if you're using VSCode.

For Javascript, you can just open the browser console. But an even better way is using an extension like Quokka that even in the free version already helps a lot to quickly verify if what you want to do will work or not.

For more features and details check out the official docs https://quokkajs.com/

Used to be true, but between Quokka.js for quick prototypes, Wallaby.js for running tests smartly within the IDE, and now Console Ninja which enables inline console.log within the VSCode while running servers for common tooling (webpack, vite). As well as continuously improving collaboration tools like Live Share, And it's become hard for me to find an argument that Webstorm is still better for productivity here.

I use https://quokkajs.com/ it has a free version!

There are some fantastic tools such as Quokka which make "more algorithmic" development very interactive and fun

There's also extensions like https://quokkajs.com/