Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration strategy with different versions of Storybook+VTA (so that there is only one filter UI) #28683

Closed
Tracked by #28388
yannbf opened this issue Jul 23, 2024 · 1 comment · Fixed by chromaui/addon-visual-tests#332
Assignees

Comments

@yannbf
Copy link
Member

yannbf commented Jul 23, 2024

  • Old VTA in new SB will use the new filter UI with no issue because the new filter UI uses the status API which the VTA has always used. Old filter UI is ignored (not applied).
  • New VTA in old SB will still apply the old filter UI, and that will work as it used to. It will send an onClick property for the story statuses, but that will be ignored by the old SB.
  • New VTA in new SB will try to apply the old filter UI but it will be ignored. Instead it will use the new filter UI.
@ghengeveld
Copy link
Member

ghengeveld commented Jul 31, 2024

@ghengeveld ghengeveld changed the title Migration strategy with different versions of Storybook+VTA (so that there is only filter UI) Migration strategy with different versions of Storybook+VTA (so that there is only one filter UI) Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants