Call it a node pack, not a plugin
"Plugin" is not ComfyUI's vocabulary. What Manager installs into custom_nodes/ is a custom node pack, and what the Registry publishes is a "node" — so to someone browsing the Registry, "plugin" reads slightly off-ecosystem, like calling a VS Code extension an add-on. The README is the listing page, so the wording is user-facing. Replaces the eight occurrences with "node pack", "the nodes", or "this pack" as each sentence reads best. "Extension" stays reserved for its narrow ComfyUI meaning: the frontend JS registered via app.registerExtension, which is web/styleref.js and nothing else. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
9e723479f8
commit
fa4e214eb1
+1
-1
@@ -29,7 +29,7 @@ from styleref_api import DEFAULT_API_BASE, StyleRefError, request_json, site_ori
|
||||
|
||||
# Identical to the CLI's scope set on purpose: the two tools share one
|
||||
# credentials file, so a login from either must satisfy both. (`extract` is in
|
||||
# the set for the CLI's sake; the plugin doesn't extract — that lives on the web
|
||||
# the set for the CLI's sake; these nodes don't extract — that lives on the web
|
||||
# app, where you can preview and refine the result.)
|
||||
SCOPES = "styles:read styles:write extract"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user