-
Notifications
You must be signed in to change notification settings - Fork 26
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
Validity / Visibility should have an inverse
attribute
#49
Comments
More examples:
The The attribute should allow the |
end2endzone
added a commit
that referenced
this issue
Aug 4, 2020
…ith tests. Modified Validator::Validate() to support the new 'inverse' attribute. Created new TestValidator.* unit tests for the new 'inverse' attribute. For issue #49.
end2endzone
added a commit
that referenced
this issue
Aug 4, 2020
…dity> elements. Fixed a bug in Validator::operator=() which was not copying 'inverse' attributes. For issue #49.
end2endzone
added a commit
that referenced
this issue
Aug 4, 2020
…ribute documentation. For issue #49.
end2endzone
added a commit
that referenced
this issue
Aug 4, 2020
* feature-issue49: Created more unit tests to back up the statement in the `inverse` attribute documentation. For issue #49. Updated documentation of `inverse` attribute of <visibility> and <validity> elements. For issue #49. Implemented parsing of attribute 'inverse' for <visibility> and <validity> elements. Fixed a bug in Validator::operator=() which was not copying 'inverse' attributes. For issue #49. Implemented Validator::GetInverse(), SetInverse() and Is Inversed() with tests. Modified Validator::Validate() to support the new 'inverse' attribute. Created new TestValidator.* unit tests for the new 'inverse' attribute. For issue #49. Enabled building of branch on appveyor.
Feature implemented in master branch in commit 455192c. |
end2endzone
added a commit
that referenced
this issue
Aug 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Validity / Visibility
xml element in Configuration Files should have an attribute to inverse the logic of the validity/visibility. For instance, inverse thefileextensions
attribute.A typical use case is the following:
split file
menu accept only a single file. When executed, it generates multiple files of which the first "part" has the file extension001
.join files
menu accept all files that matchesfileextensions="001"
Edit:
To prevent the
split file
menu to be displayed when user selects a *.001 file (we don't need to split a file twice), the menu should also not accept files that matchesfileextensions="001"
.In the end, the
split file
menu validity should be:001
.The validity element should look like this:
The text was updated successfully, but these errors were encountered: