Static component names

[devinbost]

Feature Request

When a flow is exported and re-imported into LangFlow, the component IDs change. When that flow is used in an app with tweaks, however, unless the original environment is still available that created the flow, changes to the flow result in new IDs, which break the component IDs used in the flow tweaks. The component name can be referenced in some cases, but if more than one component of a given type exists, this doesn't work. It would be ideal if components could be given static names that wouldn't change across upgrades or imports/exports - that way, they would have stable references for app development.

Motivation

We need more stable lifecycle and upgrade paths for the flows when Langflow is used as a backend endpoint.

Your Contribution

No response