Skip to content

pkg: Display error message when no dependencies exist in dune-project #11573

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Leonidas-from-XIV
Copy link
Collaborator

As a follow-up/replacement of #11555 this PR displays an warning if the package to be locked is declared in dune-project but has no dependencies.

I could imagine an additional step of reading the OPAM file and actually erroring out if it has dependencies declared there. That sounds like something we don't want to support. WDYT?

@gridbugs
Copy link
Collaborator

Can you add a test of the new behaviour.

Signed-off-by: Marek Kubica <[email protected]>
Signed-off-by: Marek Kubica <[email protected]>
@Leonidas-from-XIV
Copy link
Collaborator Author

There is something really wrong that it displays the warning 4 times (which at least points to the fact that we're doing 4x as much work as we should), I'm investigating this.

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

Successfully merging this pull request may close these issues.

3 participants