Namespace vendored H3 nodes under Dumas
This commit is contained in:
@@ -9,11 +9,19 @@ upstream packs used by the MiniMax H3 workflow:
|
||||
- `vendor/dumas_minimax_h3_refmod/`
|
||||
- `vendor/dumas_h3_refmod_picker/`
|
||||
|
||||
Their registrations and browser extensions are loaded by DUMAS, and their
|
||||
display names are prefixed with `DUMAS`. The upstream node IDs are retained so
|
||||
the full upstream UI and saved workflows remain compatible. Do not install the
|
||||
three original packs at the same time as this vendored copy, or ComfyUI will
|
||||
load duplicate node IDs and duplicate server routes.
|
||||
Their registrations and browser extensions are loaded by DUMAS. Every vendored
|
||||
node is registered with a stable DUMAS-prefixed ID and under a DUMAS category:
|
||||
|
||||
- `DumasH3Continuum_*` → `Dumas/MiniMax H3/Continuum`
|
||||
- `DumasMiniMaxH3RefMod_*` → `Dumas/MiniMax H3/RefMod`
|
||||
- `DumasH3RefModPicker_*` → `Dumas/MiniMax H3/RefMod Picker`
|
||||
|
||||
This prevents the vendored nodes from replacing or colliding with an upstream
|
||||
node of the same name. Existing workflows that use the upstream IDs are not
|
||||
silently rewritten; they must continue to use the upstream pack or be
|
||||
reconnected to the DUMAS nodes. The original packs should still not be loaded
|
||||
alongside this copy because their server routes can overlap even though the
|
||||
node IDs are now isolated.
|
||||
|
||||
The upstream source is imported as git subtrees, making future reviews and
|
||||
selective updates possible without losing provenance. DUMAS-specific changes
|
||||
|
||||
Reference in New Issue
Block a user