Document that extensions should be stateless - #6010
Open
JonnasFigueiredo wants to merge 1 commit into
Open
Conversation
The "Registering Extensions" page did not mention how often an extension is instantiated or that a single instance is typically reused across tests. Add a short section clarifying that no assumptions should be made about extension instantiation, that extensions should be stateless, and that state should be kept in the ExtensionContext.Store, linking to "Keeping State in Extensions". Signed-off-by: Jonnas Figueiredo <125215987+JonnasFigueiredo@users.noreply.github.com>
JonnasFigueiredo
force-pushed
the
docs/extension-instances-state
branch
from
August 26, 2026 00:13
4608bfa to
bdd21cf
Compare
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
1 participant
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.
Closes #6004.
The "Registering Extensions" page explains how to register extensions but does not mention how often an extension is instantiated or that a single instance is typically reused across tests, which led to the confusion in #6004.
As @mpkorstanje noted there, it shouldn't matter how often an extension is created — state should be kept in the
ExtensionContext.Store, not in the extension instance. This adds a short "Extension Instances and State" section toregistering-extensions.adocmaking that explicit and linking to "Keeping State in Extensions".