fix(storybook): handle inherited config correctly when identifying the framework used for inferred tasks #22953
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.
Current Behavior
When inferring Storybook tasks and identifying the framework used in the Storybook configuration, the project
.storybook/main.{js|ts}
file is scanned using AST to get theframework
property. This doesn't account for the framework to have been defined in a base/parent configuration file that's merged into the project Storybook configuration. Therefore, the framework is not correctly identified in such cases.Expected Behavior
When inferring Storybook tasks, the framework should be correctly identified regardless of where it was defined (project config or base/parent config).
Related Issue(s)
Fixes #