-
Notifications
You must be signed in to change notification settings - Fork 29
Improve Create Section: add open case condition and dedicated fields #1225
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
Merged
Merged
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
b225717
Add openCaseCondition, caseName, ownerId, ownerIdCondition fields
jingcheng16 472b3da
Refactor: add a helper to add create property node
jingcheng16 d130ae5
Promote per-property relevant to openCaseCondition
jingcheng16 e85d3ed
Repurpose createProperty for arbitrary case properties
jingcheng16 56c5243
Merge legacy update properties into createProperty on parse
jingcheng16 aec64e3
Add XPath validation for openCaseCondition and ownerIdCondition
jingcheng16 e49a244
Refactor: Extract promoteStashedCreateBindRelevants and ...
jingcheng16 5c0c6ed
Add tests for create section improvements
jingcheng16 60a076b
Move the stashed relevant to mug itself
jingcheng16 27fdf37
lint
jingcheng16 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see this
delete mug.p.propertypattern elsewhere in Vellum. Have you confirmed that it works? Might be better to usemug.p.set('property'), which deletes'property'from the mug's properties.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahhh, sorry, this is confusing.
_caseTypeRelevant,_caseNameRelevant,_ownerIdRelevanttechnically are not spec properties on mug, they're just plain JS property onMugPropertiesobject.mug.p.set('attr')won't work because it deletes from__data. But I can see it is confusing because the pattern ismug.p.attr... I've now moved them tomug._stashedCreateBindRelevantsto avoid confusion. 60a076b