docs: drop erroneous .plugins from provider names#88
Merged
Conversation
Provider names are entry-point names (`dynamic_metadata.regex`), never module paths. The prose in plugins.md wrote `dynamic_metadata.plugins.regex`; the section intros already used the correct form. Assisted-by: ClaudeCode:claude-opus-4.8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 AI text below 🤖
The bundled-plugin descriptions in
docs/plugins.mdreferred to plugins asdynamic_metadata.plugins.<name>, but a provider name is the entry-point namedynamic_metadata.<name>— no.pluginssegment. The section intro and code examples already used the correct form; only the opening prose of each section was wrong.Spotted in scikit-build/SIMPLE-Py#55.
The
_process_dynamic_metadatareference inplugin_authors.mdis left as-is: it is a real importable helper inplugins/__init__.py, not a provider name.