Repository navigation
Validation feature implemented - #53
Merged
Merged
Conversation
Member
|
Have a look at what I have implemented recently. Maybe you also want these errors explained so the users know what they should work on and correct. |
Member
Author
arlange
approved these changes
Nov 4, 2026
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.
Adds
POST /api/vsum/validate, which checks a project like a build does before Maven runs, without building it. The platform calls it after every auto-save to show problems as warnings while users edit (vitruv-tools/Vitruv-UI-Methodologist#635)./api/vsum/build.200with{ valid, problems }, also for invalid projects;validisfalseif there are any problems. Returns400only for malformed requests.MetamodelProcessorandReactionsProcessornow have acheck(...)method that runs in memory, andprocess()calls it before writing the project.max-concurrent-builds), so it never waits behind a running build.Like the build, the checks stop at the first stage with problems: reactions are only checked once the metamodels are valid. Empty uploads are rejected with
400, as for builds.