-
Notifications
You must be signed in to change notification settings - Fork 9
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
Don't require deps.edn
for local scripts
#85
base: main
Are you sure you want to change the base?
Don't require deps.edn
for local scripts
#85
Conversation
With the bbin changes in 64025cc, I can install the
|
@teodorlu Cool. Perhaps bb.edn should be prioritized over deps.edn, what do you think? |
Thanks for the PR, taking a closer look now. |
Yeah, that's probably the right choice! I'll make the change. |
Note: currently, this is just a start! But I wanted to put some code up so that we can discuss real code rather than hypothetical code.
|
Rationale: `bb.edn` is _meant_ to control babashka-things, and may _optionally refer_ to `deps.edn` for additional dependencies.
Makes sense. The main thing I'm thinking about is backwards-compatibility. Whatever change we make, I want to ensure we're only adding behavior and existing users don't have to do anything differently. |
100 % agreed! Let's not break userspace. |
Some observations while working on this code, probably out of scope for this PR:
(I may be missing things, as I've only focused on scripts installed from local directories) |
@teodorlu: I agree that those are out-of-scope, but you're welcome to create issues for those and anything else that comes up. |
Please answer the following questions and leave the below in as part of your PR.