capella
capella copied to clipboard
eclipse-capella
[555096] Pluggable Validation Traversal
- Tune the DiagnosticianProvider extension point so that multiple providers can be contributed. The current active provider can then be selected via preference. Commandline validation adds an optional parameter to override the provider to use.
Two providers are available by default:
- The standard tree plus part-type validation (default)
- An extended traversal with the following extra validations:
- Allocated functions
- Deployed components
- Component and Functional Exchanges between validated Components
- Interfaces between validated component ports
- Cleanup/refactoring of Capella validation code.
Signed-off-by: Felix Dorner [email protected]
can you rebase it as both gmf commits are already available on master by #190
Philippe, thanks for your comments. I dont' know I didnt get a notification or anything from Github :/ I'll check your stuff and commit requested changes.
As for the EPF validation: I'm not sure how you would want to handle this.. Should the EPF file include whether to use Tree or Extended Validation? TBH, I would probably revamp the whole system: A validation can be seen as a launch configuration, we would "run" validations, where users could select/define/store even more parameters, e.g. which elements to validate, which rules to use, and which traversal option.
SonarCloud Quality Gate failed.
0 Bugs
0 Vulnerabilities (and 
0 Security Hotspots to review)
35 Code Smells
0.0% Coverage
0.0% Duplication
![sonarqubecloud[bot] avatar](https://avatars.githubusercontent.com/in/12526?v=4 "Published by a pub.dev verified publisher"){kind=small}
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
35 Code Smells
No Coverage information
0.0% Duplication