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

📂 Migrate to a monorepo 📂 #18

Open
cabaucom376 opened this issue Jan 21, 2025 · 0 comments
Open

📂 Migrate to a monorepo 📂 #18

cabaucom376 opened this issue Jan 21, 2025 · 0 comments

Comments

@cabaucom376
Copy link
Collaborator

cabaucom376 commented Jan 21, 2025

Note: This issue is a work in progress and is subject to change

Summary

The fl_nodes package could benefit from splitting into multiple packages to not only separate concerns, but also give users a choice in what functionality they wish to adopt within their projects.

Proposal

  1. Convert this repo into 4 distinct packages:
    • fl_nodes: A full featured drop in node editing experience that has hand crafted widgets, tasteful prebuilt styles, editing conveniences, and flow execution capabilities.
      • fl_nodes_core: A low level library for constructing nodes and their relationships.
      • fl_nodes_exec: Provides an execution engine.
      • fl_nodes_util: Provides functionalities such as [ cut | copy | paste ], [ save | load ] functionality, and more.
  2. Consider implementing Melos for package management.
  3. Consider CI/CD pipeline refinements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant