Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disparity between "must" and "error-message" #50

Open
AjeyBharadwaj opened this issue Jul 21, 2020 · 3 comments
Open

Disparity between "must" and "error-message" #50

AjeyBharadwaj opened this issue Jul 21, 2020 · 3 comments

Comments

@AjeyBharadwaj
Copy link

The "must" constraint expects "is-async" field to be false. But, error says : "sw-activate is only supported as async command"

@fgruman
Copy link

fgruman commented Jul 21, 2020

I'll investigate and sent a query to the modeling team. But I believe you are correct.
If so, then all of the must statements associated with is-async may be incorrect in this module (3 instances identified).

EXISTING:
container sw-activate {
when "../command = 'sw-activate'";
must "is-async != 'true'" {
error-message "sw-activate is only supported as async command";
}
CHECKING if it should be:
grouping sw-activate-command {
description
"sw-activate-command";
container sw-activate {
when "../command = 'sw-activate'";
must "is-async = 'true'" {
error-message "sw-activate is only supported as async command";
}

@fgruman
Copy link

fgruman commented Sep 15, 2020

@AjeyBharadwaj
this is planned to be fixed in the MSAv8.0 release

@fgruman
Copy link

fgruman commented Mar 10, 2021

@AjeyBharadwaj
This has been fixed in MSAv8.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants