[Feature Request] Custom API node IDs
Open
Feature
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
Currently, all nodes are accessible by an ID that is, strangely, a string of an int based on the order in which they were added to the UI.
This isn't ideal, obviously, because when scripting to an API with common processes for multiple workflows, you need to go in to the json and manually change all the node IDs to match, which means changing all the inherited IDs in other nodes that use their output.
If we could set custom IDs in the UI like, say "global_inputs", we could just spit out the API json format and run with it.
Contributor guide
Assessment
This issue has not been assessed yet.