8000 Default Templates · Issue #335 · Canop/bacon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Default Templates #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
mkohlhaas opened this issue Mar 5, 2025 · 2 comments
Open

Default Templates #335

mkohlhaas opened this issue Mar 5, 2025 · 2 comments

Comments

@mkohlhaas
Copy link

Could we have default 8000 templates for the different analyzers bacon supports?

e.g.

bacon --init --cpp
bacon --init --python
bacon --init --js

or:

bacon --init --analyzer cpp
bacon --init --analyzer python
bacon --init --analyzer js

default being rust.

Or even better supporting build systems for C++:

bacon --init --meson
bacon --init --cmake
bacon --init --scons
...
@Canop
Copy link
Owner
Canop commented Mar 5, 2025

This might be a good idea.

I'm waiting for opinions here.

@c-git
Copy link
Contributor
c-git commented Mar 5, 2025 •
edited
Loading

I only use bacon for rust right now so I don't have a horse in the race. However, personally I no longer use much from the default job file because it's already included by default and thus I mostly empty it out and just keep and modify the ones that are special for that project. I could see this being useful if for example I wanted to use the same job names across languages and wanted a way to do that but I'd be concerned that in each project I'd need to maintain any updates I make to those defaults I want for all projects that I now specify in prefs.toml. I'm uncertain as to how I feel personally as it haven't not actually used it but sharing what I do in case that's of any value.

With regard to if it's a good idea in general though, I think it would be good as it allows for more workflows (even if those don't work for me). My only concern is the curation of the templates. It would be good if there was an easy way to get community feedback on those from people who regularly use them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Canop @c-git @mkohlhaas
0