Unify solution validation into a single ValidateSolution task - #113
Merged
TomProkop merged 1 commit intoAug 19, 2026
Conversation
zekelinAlex
deleted the
users/alexander.zekelin/unified-solution-validation
branch
August 19, 2026 11:30
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
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.
Replaces the piecemeal validation wiring with one ValidateSolution task that runs the whole single-solution pipeline (XSD/JSON schemas, duplicate GUIDs, model and manifest rules) from TALXIS.Platform.Metadata.Validation. It's wired into the solution build before packaging (opt out with SkipSolutionValidation or SkipValidation), and the separate duplicate-GUID target left the chain since the unified pass covers it. Findings that carry a rule code now log under it (TXM001, ...), so a single rule can be silenced with NoWarn. Relationship rules don't run here anymore, they're workspace-scoped now and will hook into the slnx build separately.
Note: this needs the platform-metadata release that ships SolutionValidator (TALXIS/platform-metadata#76). Package pins stay at the published 0.8.0 until then, so the Tasks project won't build yet.