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
The Microsoft #devskim project looks great, but it could use some #dev activity.
There is a great opportunity to improve the #vscode plugin or the #cli tool or to improve it's current default ruleset. You can use this tool for #security in your code, or common best practices.
Will you help me popularize it's usage? For me it's a serious contestant for the sluggish #sonarcube if it gets a bit more love 🩷
So over the past year I have been using #vscode for my #rstats and #python work. my workplace is trying to move to a unified IDE, and vscode allows remote access and WSL integration for free. However, so far it fails to spark joy in me like #RStudio (despite lack of #vim mode) and #PyCharm do. Everything feels clunky, and subpar. The "intelligent" and linting things are also quite broken in R... Has there been extensions that fundamentally change the vscode experience that I should be trying?
In the past few months, I created a bunch of Docker 🐳 tutorials covering random topics, from a fun setting for a Python 🐍 environment on the CLI to advanced topics such as multi-stage builds 🏗️. I organized all the tutorials under one folder, and I plan to keep updating this folder with future-related ones 😎.
Currently on my Docker tutorial TODO list:
➡️ Docker ENTRYPOINT vs CMD
➡️ Docker multi-architecture build
I feel like the only complaint I have of #Kate, is that I use text editors like Kate/#VSCode a lot for searching certain keywords - this is a common use case I'm sure.
On VS Code this is easy, on Kate it can/should be too... except the arrows to go to the next or earlier iteration keeps moving when it reaches the very first iteration or very last iteration. It's such a little thing but genuinely frustrating - only bcos it is a very common use case when you're using a text editor like it.