Skip to content

fix: cache many components per container #207

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 6, 2022
Merged

fix: cache many components per container #207

merged 1 commit into from
Oct 6, 2022

Conversation

yanick
Copy link
Collaborator

@yanick yanick commented Sep 6, 2022

The way the cache was set up, we could only have one render
element per test. Which, mind you, is the most common use-case,
but it can create surprises.

Fixes #205

The way the cache was set up, we could only have one render
element per test. Which, mind you, is the most common use-case,
but it can create surprises.

Fixes #205
@yanick yanick changed the title cache many components per container fix: cache many components per container Sep 6, 2022
@yanick yanick merged commit 373a666 into main Oct 6, 2022
@github-actions
Copy link

github-actions bot commented Oct 6, 2022

🎉 This PR is included in version 3.2.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@mcous mcous deleted the gh205-cleanup branch June 2, 2024 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Confused about cleanup
1 participant