docs: clarify lazyLoad.after behavior and mention luaConfig.post #4049
+38
−4
Conversation
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
GaetanLepage
approved these changes
Dec 9, 2025
Member
GaetanLepage
left a comment
GaetanLepage
left a comment
There was a problem hiding this comment.
Thanks a lot for taking the time to improve the docs.
LGTM!
yzx9
force-pushed
the
docs-lazy-load-hook
branch
from
666d3ca to
b42374e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR updates the Lazy Loading user guide to better explain how per-plugin
lazy loading works and how
lazyLoad.settings.afterinteracts with theauto-generated setup code.
This should make it clearer when to override
aftervs. when to useluaConfig.postfor post-setup configuration (e.g. configuring another plugin'scolors after a colorscheme is loaded).
close #4048