RFC: Node configuration redesign — unify services.json sections, freeze getServiceSchemas #1597
stepmikhaylov
started this conversation in
Ideas
Replies: 2 comments
🤖 Internal: Discord sync markerAuto-managed by the Discord notification workflow. Stores the linked Discord message ID and forum thread ID. Do not edit or delete. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Branch
refactor/node-config— implementation of this redesign.Docs
docs/README-node-schema.md— reference for the final schema format.New Schema services.new.json
Status
chat,dropper,webhook,filesys,parse,qdrant, theresponsefamily (9 nodes), and thegoogletool family (5 nodes) — 20 services across 8 node directories, plus the sharedcoreproperty libraries.services.cppnow fully expands every property — references,useoverrides, grouped subsections, arrays, enum branches — into the resolved schema, using a small, flat set of notations (plain fields,constant,oauth2,upload, andhidden/secret/readonly/requiredflags) instead of the old RJSF-oriented vocabulary.services.new.json, the current final schema for all converted nodes.All reactions