-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #565 from chromaui/docs_move_storybook_error_secti…
…on_into_faq Docs: Adjust FAQ entry
- Loading branch information
Showing
3 changed files
with
13 additions
and
8 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -378,10 +378,3 @@ If styles are not rendering correctly, there could be several reasons behind tha | |
If you have additional questions, use our **in-app chat** to contact or email us at [[email protected]](mailto:[email protected]). | ||
|
||
</details> | ||
|
||
<details> | ||
<summary>What is my build failing with component errors?</summary> | ||
|
||
When a story fails to render it will be badged with “Component Error”. You will not be able to “pass” a build that has component errors. Fix story errors in Storybook and run the build again. | ||
|
||
</details> |
12 changes: 12 additions & 0 deletions
12
src/content/troubleshooting/faq/build-fails-component-errors.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
layout: "../../../layouts/FAQLayout.astro" | ||
sidebar: { hide: true } | ||
title: Why is my build failing with component errors? | ||
section: "uiTestsAndReview" | ||
--- | ||
|
||
# Why is my build failing with component errors? | ||
|
||
When a test fails to render, the associated build will be badged with a "Component error" label. This means that Chromatic cannot render one or more components, which will prevent you from accepting the changes and passing the build. We recommend fixing the associated errors and re-running the build to ensure your tests pass. If you need guidance on fixing the errors, please refer to our [troubleshooting snapshots guide](/docs/troubleshooting-snapshots). | ||
|
||
If you're still having trouble, contact us via our in-app chat or email us at [email protected]. |