Add data-aware Declare constraints to path search - #15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change introduces data-aware Declare constraints for constrained path
discovery in LTSVisualizer.
The implementation covers the full workflow:
target;
The side panel and condition editor were also improved to make the larger
constraint workflow easier to use.
Main changes
Declare constraint model
Constrained path search
be discovered without requiring a fixed destination state.
Graph-aware constraint builder
Nested and multidimensional data
different levels of the same path.
typed values, existence operators, mixed sources, and repeated fields.
User-interface improvements
Supported condition capabilities
Conditions can be configured against transition
inputsandoutputsusing:null;exists;does-not-exist;Multiple configured conditions are combined as an AND group.
Compatibility
The change preserves:
No graph JSON or condition serialization migration is required.
Validation
The following validation was completed:
npm testnpm run buildnpm run build:offlinenpm run devManual regression testing covered:
existsanddoes-not-exist;Scope
This PR combines the complete Declare-constraint feature because the model,
monitor framework, path-search integration, graph-derived data catalogue, and
constraint editor depend on one another as a single end-to-end workflow.