[Blueprints] Make landingPage handling runtime-specific and move it to PlaygroundViewport #1916
+42
−16
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.
Moves the
playground.goTo(blueprint.landingPage)
call from thecompile()
method to thePlaygroundViewport
component to:?url=/wp-admin/
on OPFS sites, not just on the temporary sitesgoTo
method in all Blueprints. It setsiframe.src
which is browser-specific..goTo()
is not available in, say, Playground CLI or Studio. Those runtimes would need their own handlers to support the landing page.Remaining work
compile()
Testing instructions
For temporary sites:
url
parameter is still present in the address barFor stored sites:
?url=/wp-admin/
and visit iturl
parameter is removed from the address barcc @akirk @brandonpayton @bgrgicak