Refactor to tags for allow/block lists of nodes
Closed this issue · 1 comments
Right now the Graph uses a [IncludeModules] attribute to specify module paths that are allowed to be added through the editor. But I typically run into use cases of Graph A having it's own flow control nodes under /Flow Control and Graph B also having its own under /Flow Control. I could rename these to avoid the conflict, but I think a better long term solution would be to just assign a flat list of tags to nodes and have allow/block attributes on a Graph for tags.
This'll also make it easier to implement #3 as we don't need all the extra logic to walk down module paths.
Modules themselves can stay, but it'll just be a representation of how it's listed/grouped in the search results. Maybe renamed to something besides module (just path or searchPath?)
🎉 This issue has been resolved in version 1.0.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀