Community
Participate
Working Groups
We still have too many false negatives in validation errors to enable this, but when we get to a point where we're confident that most are fixed, we should consider enabling live validation in the VSM editor, and/or validation on save. Instead of an all or nothing approach, maybe we could identify different subsets of validation rules, and enable them at different points: 1. Ones which are fast to execute and have a null/low rate of false negatives could be executed live during edition. 2. Slower to execute but still with low rate of false negatives could be executed on saving, with a warning for saving an invalid VSM. 3. The rest would be executed only in case of on-demand validation from the specifier. In terms of ergonomics, points 1 and 2 are only reasonable if the rate of false negatives are really low, and if the resulting validation warnings/errors do not interfere with the workflow (e.g. we don't want a popup to appear on *every* save, just because Sirius can not validate some part of the VSM that the specifier knows will work, or doesn't care for now).
