Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

phiSgr
Copy link
Collaborator

@phiSgr phiSgr commented May 2, 2024

Is the mermaid diagram worth it? IDK

Copy link

vercel bot commented May 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
company-landing ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 14, 2024 7:30pm
framework-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 14, 2024 7:30pm
framework-landing ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 14, 2024 7:30pm
moose-product-analytics ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 14, 2024 7:30pm

state: discussion
---

## Objective
Copy link
Collaborator

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants