-
Notifications
You must be signed in to change notification settings - Fork 4k
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
It should be possible to use the same extension as both a production and dev dependency #14635
Comments
I would hope that if a dev and production rule tried to create the same named workspace an error would be thrown. I think that's probably inevitable given my mental model of how this works, but best to check |
Current thinking is to make the My original thinking was that we could introduce some sort of scoping construct within MODULE.bazel files, to make several statements "dev" (read: effective only in the root module), instead of having |
Fixes bazelbuild#14635. PiperOrigin-RevId: 432155351
Fixes #14635. PiperOrigin-RevId: 432155351
Description of the problem / feature request:
It's often useful to use the same extension as both a production and development time dependency. eg.
When one tries this, the following error is shown:
As an aside, this message not include the name of the extension which makes debugging harder.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
See above
What's the output of
bazel info release
?release 5.0.0
The text was updated successfully, but these errors were encountered: