-
-
Notifications
You must be signed in to change notification settings - Fork 339
feat: add support for nesting vue flows #1895
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
base: master
Are you sure you want to change the base?
Conversation
This might be temporary, but it is needed to allow nesting flows. Workarounds are desired.
…th ancestorZoom Co-authored-by: plc-dev <[email protected]>
…le bounds calculations Co-authored-by: plc-dev <[email protected]>
Will fix this soon
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
@simonmysun is attempting to deploy a commit to the Burak Cakmakoglu's projects Team on Vercel. A member of the Team first needs to authorize it. |
🚀 What's changed?
This draft pull request introduces support for nesting vue-flow components. Different from what's demonstrated in the nesting nodes example, this allows vue-flow instances to be nested.
/nesting-flows
and/recursive-nesting-flows
inexamples/vite/router.ts
to demonstrate nested flow components.ancestorZoom
property inFlowProps
to track and manage zoom levels inherited from ancester vue-flow instances.ancestorZoom
🐛 Fixes
Bug fixed$\leqq$ 0
🪴 To-Dos
nopan
classnopan
class from nodes. This should be avoided otherwise it is a breaking change.panBy
and autopan functionalitiesfitView
functionality