Develop a linting config for orchestration flows #9693
Assignees
Labels
asyncFlow
related to membrane-based replay and upgrade of async functions
enhancement
New feature or request
Comments
This was referenced Jul 17, 2024
Merged
mergify bot
added a commit
that referenced
this issue
Jul 18, 2024
closes: #9692, #9693 ## Description Sets up a convention for `flows` modules and document in the orchestration README. Also makes lint config to test them. The lint config is exported as a shared config that developers can use. I've included it in the same PR to make sure it works with the new convention. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations Documented the convention in the README. I expect it'll make its way to docs.agoric.com as needed. ### Testing Considerations nothing special ### Upgrade Considerations not yet deployed
turadg
changed the title
mhofman
added
the
asyncFlow
|
This should apply to any async flow of possible |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Without E support in asyncFlow, we (OpCo) should develop a linting config to prevent developers from using E in orchestration flows.
Description of the Design
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: