digital-garbageandClaude Sonnet 5
776529e0d8
The port plan calls for every module under modules/ to declare a CATEGORY so Settings/Engine panels can group by it. Only alg, sharpen, appearance, and full_control had one; the other 12 (loaders, empty latent, media load, minimax_h3, output decode, sampling modifiers/ sampler, system pipeline) are plain infrastructure with no user-facing settings dial, so they land in "system" except output_decode (post, matching its STAGE) and the two sampling modules (sampling). Verified against core/tests (548 passed) -- category validation and the registry's field-mapping catch a typo here, per the earlier fixture-gap fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
25 lines
665 B
Python
25 lines
665 B
Python
"""The modifier nodes. A node-only module."""
|
|
|
|
from .nodes import FunPackLoadModifiers, FunPackModifierSettings
|
|
|
|
ID = "sampling_modifiers"
|
|
TITLE = "Modifiers"
|
|
STAGE = "sampling"
|
|
CATEGORY = "sampling"
|
|
STATUS = "proven"
|
|
|
|
NODES = [FunPackModifierSettings, FunPackLoadModifiers]
|
|
|
|
|
|
def settings_sink():
|
|
"""Where the values a person picked belong in a graph.
|
|
|
|
Announced rather than known: core places the app's settings into whatever a
|
|
module says accepts them, so this node is not privileged, it is merely the
|
|
one that volunteered.
|
|
"""
|
|
return {"node": "FunPackModifierSettings", "input": "settings"}
|
|
|
|
|
|
PROVIDES = {"settings_sink": settings_sink}
|