Skip to content

Slight clarification in strict dependencies error message#1424

Merged
jayconrod merged 2 commits intobazel-contrib:masterfrom
jayconrod:fix-compile-error
Apr 2, 2018
Merged

Slight clarification in strict dependencies error message#1424
jayconrod merged 2 commits intobazel-contrib:masterfrom
jayconrod:fix-compile-error

Conversation

@jayconrod
Copy link
Copy Markdown
Collaborator

No description provided.

@jayconrod jayconrod requested a review from ianthehat April 2, 2018 19:00
@jayconrod
Copy link
Copy Markdown
Collaborator Author

I added another commit to print the known dependencies, too, so it's easier to tell what the mismatch is. PTAL.

Copy link
Copy Markdown
Contributor

@ianthehat ianthehat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be a bit verbose if there are a lot of known dependancies, but it's probably not a problem worth solving.

@jayconrod jayconrod merged commit 0c8b71b into bazel-contrib:master Apr 2, 2018
@jayconrod jayconrod deleted the fix-compile-error branch April 2, 2018 20:08
@jayconrod
Copy link
Copy Markdown
Collaborator Author

It would be nice to add a "did you mean" message after each missing import instead of listing all the known imports using edit distance. I'm not aware of a simple way to do that without going beyond the standard library.

yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
This largely covers how to introduce a breaking change.

It also attempts to clarify what is or isn't a breaking change.

Closes bazel-contrib#1424
Work towards bazel-contrib#1361
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants