feat: trigger updates to IProcedureBlock blocks #6570
Merged
Conversation
This file contains 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
github-actions
bot
added
PR: feature
This was referenced Oct 20, 2022
NeilFraser
approved these changes
Oct 24, 2022
BeksOmega
force-pushed
the
feat/trigger-procedure-updates
branch
from
af7d30d to
6651814
Compare
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.
The basics
npm run formatandnpm run lintThe details
Resolves
#6515
Proposed Changes
Makes it so updates to the procedure data models actually trigger updates to blocks.
Note that the built-in blocks haven't be refactored to /respond/ to these updates. But now they could be.
Test Coverage
Enabled skipped tests!
Documentation
N/A
Additional Information
Dependent on #6569