Next: Use <<package>>::<<import>> naming convention for mock names
#26853
Conversation
This file contains 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
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 8dbd04c. 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 targetSent with 💌 from NxCloud. |
kasperpeulen
changed the title
kasperpeulen
changed the title
yannbf
reviewed
Apr 16, 2024
yannbf
reviewed
Apr 16, 2024
yannbf
reviewed
Apr 16, 2024
yannbf
reviewed
Apr 16, 2024
Co-authored-by: Yann Braga <[email protected]>
Co-authored-by: Yann Braga <[email protected]>
Co-authored-by: Yann Braga <[email protected]>
Co-authored-by: Yann Braga <[email protected]>
kasperpeulen
force-pushed
the
kasper/mock-names
branch
from
3c33eed to
8b6bbbf
Compare
JReinhold
changed the title
<<package>>::<<import>> naming convention for mock names
JReinhold
approved these changes
Apr 19, 2024
| @@ -794,7 +794,7 @@ exports[`renders nextHeaderStories stories renders Default 1`] = ` | |||
| </strong> | |||
|
|
|||
| <span> | |||
| firstName=Jane; lastName=Doe | |||
| firstName=Jane; ; lastName=Doe; | |||
There was a problem hiding this comment.
We are using now even closer what does Next does, so I guess it must be okay.
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 I did
Use a new naming convention to make actions easier to scan
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake 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 pull request has been released as version
0.0.0-pr-26853-sha-8dbd04c4. Try it out in a new sandbox by runningnpx [email protected] sandboxor in an existing project withnpx [email protected] upgrade.More information
0.0.0-pr-26853-sha-8dbd04c4kasper/mock-names8dbd04c41713273018)To request a new release of this pull request, mention the
@storybookjs/coreteam.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=26853