Skip to content

Support for git deps needing to be prepared #2950

@MikeJCusack

Description

@MikeJCusack

Some git deps have a prepare step that must be run when installing or updating the dep before it can be used. An example of this is https://github.com/djblue/portal. Currently Calva is not aware of this and the jack-in command will fail if any such deps have not been prepared. The CLI method for preparing would be clj -X:deps prepare if the dep(s) is(are) not in an alias and clj -X:deps prepare :aliases '[:alias1,:alias2,...]' if in one or more aliases. It was suggested in the Slack conversation that a gitDepsAliases custom connect sequence key could be added and if present to augment the jack-in command with the required prepare command or to provide a command for it. If no deps need preparing due to not requiring preparing at all or have already been prepared for the current dep version the result will be a no-op so it would not be costly to include on each jack-in.

Clojure official reference: https://clojure.org/guides/deps_and_cli#prep_libs
Example dep prepare definition: https://github.com/djblue/portal/blob/e376ac4469bded3fb2797b723fb06e9548ccf005/deps.edn#L8
& https://github.com/djblue/portal/blob/e376ac4469bded3fb2797b723fb06e9548ccf005/dev/tasks/build.clj#L47

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions