birdcar/devwrangler

Bringing peace, freedom, justice, and security to your Python empire

Hi there 👋

I'm one of the co-founders of Yetto, a support tool built by and for support professionals.

Bio

• 😄 Pronouns: He/Him/His
• 🏢 Current employer: Yetto
• ⚙️ Languages: .py, .js, .rs, .html, .css,
• 💬 Ask me about: git, github, static site generators, python, support operations, Yetto
• 📫 Contact me: by opening a New Discussion in my repository

devwrangler's Issues

Add Jinja 2 for templating

Right now, the JSON values for things like extensions.json are hardcoded into the code and then dumped to a file using the JSON module. This is probably not eggregiously wrong, but as devwrangler scales and starts to spawn additional files (or allows users to provide us with additional files) I'm certain we're going to want to have more flexibility and extensibility.

In my mind, the right solution here would be to add Jinja2 as a dependency and then maintain a folder of template files in the CLI's source directory. We could then add some very basic logic to the templates to determine what should or shouldn't exist as a feature or dependency when a user spawns a project while cleaning up our code considerably.

Add `Rich` for terminal beauty

The CLI functions but doesn't feel "fun" enough to me.

I get that that's subjective, but I'd love for it to be nice to look at and fairly clean when a user runs things. Rich is a fantastic library that allows for really beautiful terminal UI and I think it fits the bill perfectly.

VS Code's recommended extensions has moved to `extensions.json`

• Dev Wrangler version: 0.2.1
• Python version: 3.10.0
• Operating System: macOS

Description

While trying to configure a dev environment on a new laptop, I noticed that the "requirements" key in settings.json was greyed out. After reading the docs it looks like recommended extensions moved into their own file in the .vscode directory: the extensions.json file

We'll need to have pydev create that file and then move our current list of extensions out of settings.json and into the new file.

The system user for GitHub Action's macos runner lacks write permission to the tmp directory

It appears that on GitHub Action's macos runner (and only there as far as I can tell) the actions user doesn't have permission to generate the virtual environment. Specifically, it appears that user is lacking write permission to the tmp directory created by pytest:

https://github.com/birdcar/devwrangler/runs/4724004981?check_suite_focus=true#step:5:168

To this I say: WAT 👀