FlowFuse / FlowFuse/node-red-dashboard

Bug: ${UI} token in subflow ui-template ui field gets rewritten to a hardcoded ID

Open
#2,137 0 comments 0 reactions 1 assignee Claimed by @allthedoll View on GitHub
needs-triage
Dominant language
HTML
Stars
355
Forks
82
Avg merge
4d 23h
Merged PRs (30d)
24

Description

### Current Behavior

**Setup:** Subflow with a conf-types env var UI (type ui-base). Three ui-template nodes inside the subflow with "ui": "${UI}", per our docs. Packaged as an npm module via the FlowFuse Library.

### Steps To Reproduce

After deploy + refresh, the ui field is rewritten from ${UI} to a literal hex ID. On instances whose ui-base doesn't match that ID, the widget silently fails to render. No error, no node status, no log.

### Environment

- Dashboard version: 1.30.2
- Node-RED version: 4.1.10
- Platform/OS: Mac OSX
- Browser: Chrome

What's rewriting ${UI} to a literal ID on deploy?
Can we surface a warning when a subflow ui-template's ui reference is unresolvable, so this fails loud instead of silent?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.