This weekend, working on an R + Docker 🐳 workshop for the R/Medicine conference. The workshop focuses on setting up a dockerized R development environment using #vscode and the Dev Containers extension 🚀. The workshop is based on a tutorial I created last year for setting up a dockerized R development environment with #Docker VScode, and the Dev Containers extension. It is also a great opportunity to test the new Shiny extension for VScode by Posit, which was released recently 😎.
The new features I'd like #VSCode to have: proper handling of tab dragging like every other modern GUI of the past decade, i.e. move the dragged tab and the target to show drop location.
The new features VSCode adds: 'Build AI into your extensions with the Chat and Language Model API'. FFS. #NoAI
Just released #Regal v0.23.0, featuring 3 new linter rules and greatly improved completion suggestions from the language server. Try it out in the #VSCode extension for #OPA, or any other editor supporting language servers. Working with #Rego has never been easier!
Needed to rename a test fixture in a #Python file, and find/replace wasn't up for the job. So I decided to give #VSCode a go:
I started by pressing Ctrl+F2, for "Change All Occurrences". I think that is basically find/replace, and hence didn't do what I wanted.
Instead, I installed the recommended Python extension, and pressed F2 for "Rename Symbol". That claims to have only made one change, and the references to the function are still using the old name.
So, consider me confused. I'm using #pytest, whereby the test fixtures are referenced as function arguments rather than being called directly. Maybe that's what VS Code is struggling with? Either way, I've now spent more time on this than just manually editing the text.
From #Copilot, to #Azure AI and #Prompty, to their developer first focus, leading #GitHub, #VSCode being the long bet that paid off, to the future of a doctor’s bedside manner assisted with AI.
Microsoft is all-in on AI and Build 2024’s discussions and announcements proves it.
Check it out, the #Shiny extension for #VSCode now supports both Shiny for R apps and Shiny for Python apps in everyone's second favorite IDE!
Along with the updates come a few neat features for deploying your Shiny apps as serverless ShinyLive apps using https://shinylive.io, or for saving a ShinyLive app as local #RStats or #Python files.
@tjventurini Depends… PHPStorm for laravel and other framework projects. VS Code for small single file scripts, or small frameworkless projects and testing quick one offs. No reason you can’t use both right?
Does anybody know if there's a way in VS Code to tell the HTML and Markdown editors what the "root" of the site is?
I have a project where the web root lives under /site rather than / in the project, but the HTML and Markdown editors assume the root of the project == the root of the site. Short of opening just the site folder, is there a way to tell the editors where to look when doing Intellisense for links and to resolve static content in the Markdown preview?
Gotta say, VS Code and LSP have raised the bar for the baseline developer experience for all IDEs. Recently I installed an extension for shell scripts and with LSP support for the first time I have IDE support for shell scripting. It has all of the core IDE features that I would expect.
Data Wrangler is a new Microsoft VScode extension for data exploratory analysis. It supports Python 🐍 and Pandas 🐼 DataFrame objects and is integrated into VScode Jupyter Notebooks. Here are some of the functionalities of Data Wrangler:
✅ Data review
✅ Column filtering
✅ Summary statistics
✅ Data cleaning and transformation
✅ Hadeling missing values
✅ Creating new fields