Skip to content
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.

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

Feature: adding build runner command #337

Closed
JordanllHarper opened this issue Mar 20, 2024 · 3 comments
Closed

Feature: adding build runner command #337

JordanllHarper opened this issue Mar 20, 2024 · 3 comments

Comments

@JordanllHarper
Copy link
Contributor

JordanllHarper commented Mar 20, 2024

Currently, to build projects using build runner, we have to do this in a separate terminal window.

I would like to be able to run this as a command!

i.e. FlutterBuild or :DartBuild

Edit: followup, it would also be nice if we could specify the --delete-conflicting-outputs in a configuration.

@RyanCarrier
Copy link

I doubt this will get picked up, I'm not sure it makes sense to. This is a task in your dev process not flutter in particular, I have mine setup under overseer.nvim and a make file to make things easier.

https://github.com/stevearc/overseer.nvim

@JordanllHarper
Copy link
Contributor Author

That makes sense I guess. It feels pretty integral to the flutter process is my only thought. Builds are often run in flutter apps and so providing it makes more sense to me than not. Happy to close though and will check out overseer.

@JordanllHarper JordanllHarper closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2024
@RyanCarrier
Copy link

I'm not sure how planned this is but I know there has been talk for a while about potential compile time macros which would solve the whole build runner step regardless

https://github.com/dart-lang/language/blob/main/working/macros/feature-specification.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants