Angular: Fix Angular template error for props with a circular reference #28498
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.
Closes #25275, #16855
What I did
For Angular stories, two templates are generated. One for the template that will be used for rendering and another that will be used for displaying source. The problem is the way objects are handled for the source template. This provides a fix for the circular reference case.
The
computesTemplateSourceFromComponent
attempts to replace input props with a value, instead of the variable. It relies oncreateAngularInputProperty
, which usesJSON.stringify
then applies some formatting replacements. The problem is that JSON.stringify does not handle circular references.The solution I went with as an initial attempt is to use a replacer that replaces the circular reference with
"[Circular]"
. If there is a better convention then that can be changed. I wasn't sure what the best solution would be, so I just picked something.As an example of my current solution, assume I have the following:
The resulting source template should be similar to the following:
I added a test for this scenario
angular source decorator > with argTypes (from compodoc) > should handle circular object as stringified
. Also, I added tests for thecomputesTemplateFromComponent
and updated a few test descriptions to not start with an uppercase, for consistency.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!
This is a matter of stringifying an object, so I don't think a manual testing process is necessary. I can try to find a spot to put a story, if needed. Running the unit test should be enough, but if you want to use a sandbox then you can pass an object to and input prop. The docs addon would also need to be loaded, so
sourceDecorator
gets called.Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/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>