Skip to content

Build: Exclude server action stories to run in next 13#29592

Merged
yannbf merged 1 commit into
nextfrom
yann/fix-next-13-sandboxes
Nov 12, 2024
Merged

Build: Exclude server action stories to run in next 13#29592
yannbf merged 1 commit into
nextfrom
yann/fix-next-13-sandboxes

Conversation

@yannbf
Copy link
Copy Markdown
Member

@yannbf yannbf commented Nov 12, 2024

Closes #

What I did

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-storybook/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>

Greptile Summary

Added server action stories for Next.js pre-release template and moved existing stories to handle authentication flows with proper test coverage.

  • Added code/frameworks/nextjs/template/stories_nextjs-prerelease/ServerActions.stories.tsx with test coverage for login/logout flows
  • Added code/frameworks/nextjs/template/stories_nextjs-prerelease/server-actions.tsx implementing cookie-based authentication
  • Included workaround for React 19 beta ErrorBoundary handling using dangerouslyIgnoreUnhandledErrors
  • Added comprehensive test scenarios for both logged-in and logged-out states with proper assertions

@yannbf yannbf added bug build Internal-facing build tooling & test updates ci:normal Run our default set of CI jobs (choose this for most PRs). patch:yes Bugfix & documentation PR that need to be picked to main branch and removed bug labels Nov 12, 2024
@yannbf yannbf merged commit 0676c9c into next Nov 12, 2024
@yannbf yannbf deleted the yann/fix-next-13-sandboxes branch November 12, 2024 10:30
@nx-cloud
Copy link
Copy Markdown

nx-cloud Bot commented Nov 12, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 12be898. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

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

4 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile

test: {
// This is needed until Next will update to the React 19 beta: https://github.com/vercel/next.js/pull/65058
// In the React 19 beta ErrorBoundary errors (such as redirect) are only logged, and not thrown.
// We will also suspress console.error logs for re the console.error logs for redirect in the next framework.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

syntax: typo in 'suspress' - should be 'suppress'

import { redirect } from 'next/navigation';

export async function accessRoute() {
const user = (await cookies()).get('user');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

style: Potential race condition - cookies() is called twice, once for await and once for get(). Use const cookieStore = await cookies() first

}

export async function login() {
(await cookies()).set('user', 'storybookjs');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

style: No expiration time set for cookie, could lead to indefinite sessions

Comment on lines +14 to +15
revalidatePath('/');
redirect(`/protected`);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

logic: Calling revalidatePath() right before redirect() is unnecessary since the redirect will trigger a full page load

yannbf added a commit that referenced this pull request Nov 13, 2024
Build: Exclude server action stories to run in next 13
(cherry picked from commit 0676c9c)
@github-actions github-actions Bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Nov 13, 2024
@ndelangen ndelangen removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Internal-facing build tooling & test updates ci:normal Run our default set of CI jobs (choose this for most PRs). patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants