Closed Coffee2Bits closed 2 months ago
Not currently being experienced in 0.4.0 because the constrainer was not brought forward and converted. The conversion task for this is #741 . That potentially the conversion could make use of the dataref
primitive constraint since it is the constraint that runs when checking referenced definitions.
If it is decided that the legacy validator needs to be reimplemented as a constraint, want to be sure that the output remains helpful and does not become overwhelming again.
Scope to only run within "user editable" (in legacy AaC there was a field entry for flagging this, not sure if that was carried forward in 0.4.0 work) files, or user defined files, not to entire language context and therefore ALL definitions within AaC when running check
on a file. Scope to only checking within the passed in file and any imported files maybe?
Based on the results of the 0.4.0 implementation and the current thoughts on the unreferenced constraint not being needed currently, this issue is being closed.
Pre-requisites
What version of the AaC package are you using? Check your version with the command: aac version.
0.2.17
Description
The new validation that checks for unreferenced definitions is producing overwhelming output. It's a combination of issues including false-positives and some edge cases. When I run validation on the usecase for the alarm clock model I get this massive output:
Reproduction URL
https://github.com/DevOps-MBSE/AaC
Reproduction steps
Screenshots
No response
Logs
Pertinent Files
In repo