-
Notifications
You must be signed in to change notification settings - Fork 10
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
RFD-0004: Diagram with regular flow and migration flow. #1150
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
state: discussion | ||
--- | ||
|
||
## Objective |
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.
Perhaps this proposal is missing a WHY? Why is this important - other than the potential to unify flows?
We can probably simplify the implementation | ||
(at the cost of worse performance, as noted above). | ||
|
||
### User Impact |
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.
How does this change the /flows
folder structure & file naming convention, if any?
Is there an example flow.ts
for this new approach? I think I remember an import mapping PR and it looked clean. That could be a good way to show why this is easier to understand for users.
Is the mermaid diagram worth it? IDK