[codex] Share fake data context - #32
Merged
Merged
Conversation
k-kinzal
marked this pull request as ready for review
July 4, 2026 13:39
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.
What changed
FakeDataContextto hold one schema, oneOperationLookup, one configuredOpenAPIFaker, and the resolved faker options.Interceptorto create a single fake-data context and reuse it for operation lookup and generated responses.FakeRequestandFakeResponseto acceptFakeDataContextas a source and to route lookup/faker calls through the context.FakeDataContextas a reusable source for standalone generation.Why
Operation lookup and OpenAPI faker creation were repeated across
Interceptor,FakeRequest, andFakeResponse. This scattered the generation setup and forced hot request paths to rebuild faker state for every generated response.Impact
Existing
ServerandSchemasources continue to work. Callers that generate multiple requests/responses from the same schema can now create oneFakeDataContextand reuse it.Validation
composer testcomposer lint