You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During some testing with Storybook's beta, it seems that the Angular examples we currently provide, specifically for the Button component, are not working as expected despite implementing the @storybook/test package in the component's story file. This may have been an oversight on our part, but it should be addressed to ensure that the examples are working as expected and the output is as intended, more even so with the upcoming release of Storybook 8, as this is a feature that will probably be used more often by our users and will be the default pattern to follow. Below is a small recording of the issue in question.
angular-beta-no-actions-fn-function.mp4
This issue also has a compound effect on the examples we currently provide, not only for this framework but also for the other supported ones, to which we should ensure that our examples apply this pattern as much as possible to guarantee that the user experience is consistent across all frameworks. However, if that is not possible based on the framework's limitations, we should at least adjust the documentation to reflect the limitation as how it's currently implemented it may lead to confusion and frustration for the user as the text and code examples provide an agnostic approach of how to implement the feature which may not be the case, leading to users reaching out to us via our support channels for help and clarification on the matter which is not ideal for the user or for us, when we could have avoided this by providing the correct information from the start.
Describe the bug
During some testing with Storybook's beta, it seems that the Angular examples we currently provide, specifically for the Button component, are not working as expected despite implementing the
@storybook/test
package in the component's story file. This may have been an oversight on our part, but it should be addressed to ensure that the examples are working as expected and the output is as intended, more even so with the upcoming release of Storybook 8, as this is a feature that will probably be used more often by our users and will be the default pattern to follow. Below is a small recording of the issue in question.angular-beta-no-actions-fn-function.mp4
This issue also has a compound effect on the examples we currently provide, not only for this framework but also for the other supported ones, to which we should ensure that our examples apply this pattern as much as possible to guarantee that the user experience is consistent across all frameworks. However, if that is not possible based on the framework's limitations, we should at least adjust the documentation to reflect the limitation as how it's currently implemented it may lead to confusion and frustration for the user as the text and code examples provide an agnostic approach of how to implement the feature which may not be the case, leading to users reaching out to us via our support channels for help and clarification on the matter which is not ideal for the user or for us, when we could have avoided this by providing the correct information from the start.
cc @valentinpalkovic , @kasperpeulen @vanessayuenn
To Reproduce
System
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: