Implemented cached version of generate_oas_component()
#972
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.
I tried this after-hours and it works surprisingly well so I cleaned it up and put it here:
It caches
generate_oas_component()
calls that are repeated multiple times, like when they are part of aTestCase.setup()
or some other often re-used code like theMockAPIData
class.It works by using some funky python
hash()
code to get a cache key anddeepcopy()
to isolate each usage.Also it's obviously a memory hole, but memory and
deepcopy()
are a lot cheaper then CPU cycles running the OAS/faker stack.