Skip to content

NextJS: Use a proper web view to give loading UI#24962

Merged
shilman merged 1 commit into
shilman/nextjs-server-mockfrom
tom/loading-ui
Nov 24, 2023
Merged

NextJS: Use a proper web view to give loading UI#24962
shilman merged 1 commit into
shilman/nextjs-server-mockfrom
tom/loading-ui

Conversation

@tmeasday

Copy link
Copy Markdown
Member

Telescopes #24447

What I did

Use the standard WebView connected to some static HTML I insert similarly to the pages version

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

@tmeasday tmeasday requested a review from shilman November 23, 2023 10:31
@@ -0,0 +1,418 @@
export const previewHtml = `

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code is now in 3 places, we should figure out how to share it.

NOTE this one is slightly different as I removed the #storybook-root element.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did you remove the #storybook-root element in this one?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it is rendered by the route in the /app dir case. That's different to the usual situation where the preview picks off the static dom element and passes it to the renderer

@shilman shilman changed the title Use a proper web view to give loading UI NextJS: Use a proper web view to give loading UI Nov 24, 2023
@shilman shilman merged commit 99a0e69 into shilman/nextjs-server-mock Nov 24, 2023
@shilman shilman deleted the tom/loading-ui branch November 24, 2023 02:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants