Repository navigation
Drupal configuration schema read again one file at a time - #543
Merged
AJenbo merged 1 commit intoNov 6, 2026
Merged
Conversation
3 of 6 tasks
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Editing a configuration schema file, in a buffer or on disk, reads only that file again. The other files keep their parsed entries and trees, and an event whose text did not change reads nothing. A schema file changed on disk keeps its place in the list, so the first declaration of a key still wins, and closing an unsaved new configuration file of a test module drops its names. Assisted-by: claude-code/claude-opus-5-5
AJenbo
force-pushed
the
drupal-config-schema-cache
branch
from
November 6, 2026 21:36
bd52b8b to
90b175c
Compare
Contributor
|
Thanks for fixing that |
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.
Editing a Drupal configuration schema file now reads only that file again. Before, every keystroke in a
config/schema/*.schema.ymlbuffer made the next request re-read every schema file of the site. Opening, saving or closing a schema file without changing its text costs nothing. Completion, hover and go-to-definition return the same results.Two small fixes on the same path:
Follow-up to #540.
How to test: run
composer installinexamples/drupal, then openexamples/drupalwith this branch's build. Inweb/modules/custom/acme/:In
config/schema/acme.schema.yml, add these lines at the top:In
src/Form/SettingsForm.php, empty['acme.settings']ingetEditableConfigNames()and complete:acme.extrais offered.In the schema, rename
notify_email:tonotify_mail:. InSettingsForm.php, complete after'#config_target' => 'acme.settings::notify_mailis offered.Undo both edits: the old names come back.
Checklist
If applicable:
CHANGELOG.md. Not applicable: this fixes the still unreleased configuration names entry.README.md,docs/,examples/). Not applicable: no visible behaviour to document.config-schema.json). Not applicable: this PR adds or changes no setting.the changes and why they are needed.
the changelog, and other user-facing content, and removed or corrected
anything inaccurate, unclear, or unnecessary.