feat: show warnings for failed projects for --all-projects [UNIFY-1099] [UNIFY-1102]
#93
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
snyk-tim
force-pushed
the
feat/show-warnings-for-all-projects
branch
from
9a1e881 to
042447d
Compare
thomasschafer
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this does
Shows warnings for all projects being tested with
--all-projects. Relies on the--print-effective-graph-with-errorsargument added to the cli in this PR.Warning messages now include failed/total project counts (e.g.,
2/4 potential projects failed to get dependencies).Future considerations
This PR includes a temporary implementation for rendering warnings. The long-term plan is for the CLI to take full ownership of warning rendering. Achieving this will require extensions to handle
workflow.Dataobjects that contain errors and propagate them upstream rather than rendering them directly. Implementing this change will require coordinated updates across extensions to ensure backwards compatibility and avoid breakages.