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.

Sign up for GitHub

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

Jump to bottom

Don't assume <Tab /> components are available when setting the next index #2642

Merged
merged 2 commits into from
Aug 3, 2023
Merged

Don't assume <Tab /> components are available when setting the next index #2642

merged 2 commits into from
Aug 3, 2023

Commits on Aug 3, 2023

  1. only set the next index when tabs are available 

    Currently we were assuming that the `tabs` were always there, but this
    @RobinMalfait
    RobinMalfait committed Aug 3, 2023
    Configuration menu
    Copy the full SHA
    e4e3374 View commit details
    Browse the repository at this point in the history

  2. update changelog

    @RobinMalfait
    RobinMalfait committed Aug 3, 2023
    Configuration menu
    Copy the full SHA
    fbc902a View commit details
    Browse the repository at this point in the history