Add playground force-destroy option#846
Merged
hatemhosny merged 3 commits intolive-codes:developfrom Jun 8, 2025
Merged
Conversation
✅ Deploy Preview for livecodes ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
felixhuttmann
force-pushed
the
add-playground-destroy-force-option
branch
from
05f8720 to
faac6e8
Compare
|
Collaborator
|
Thank you @felixhuttmann Your approach is reasonable enough to be used as the default behaviour (without having to pass any arguments). This should be available in the next SDK release. I will let you know when it is released. |
2 tasks
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
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.
What type of PR is this? (check all applicable)
Description
Add a
{ force: true }option on playground.destroy to permit destroying playground instances even when the iframe is stuck in an endless loop.Related Tickets & Documents
Fixes #845
Added tests?
Added to documentations?