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

Version Packages #7537

Merged
merged 1 commit into from
Apr 25, 2023
Merged

Version Packages #7537

merged 1 commit into from
Apr 25, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 3, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@chakra-ui/[email protected]

Major Changes

@chakra-ui/[email protected]

Minor Changes

  • #7502
    49a29a238
    Thanks @estheragbaje! - Introduce new
    Stepper component to model sequencial steps in a process.

    <Stepper index={activeStep}>
      {steps.map((step, index) => (
        <Step key={index}>
          <StepIndicator>
            <StepStatus
              complete={<StepIcon />}
              incomplete={<StepNumber />}
              active={<StepNumber />}
            />
          </StepIndicator>
    
          <Box>
            <StepTitle>{step.title}</StepTitle>
            <StepDescription>{step.description}</StepDescription>
          </Box>
    
          <StepSeparator />
        </Step>
      ))}
    </Stepper>

Patch Changes

@chakra-ui/[email protected]

Minor Changes

  • #7502
    49a29a238
    Thanks @estheragbaje! - Introduce new
    Stepper component to model sequencial steps in a process.

    <Stepper index={activeStep}>
      {steps.map((step, index) => (
        <Step key={index}>
          <StepIndicator>
            <StepStatus
              complete={<StepIcon />}
              incomplete={<StepNumber />}
              active={<StepNumber />}
            />
          </StepIndicator>
    
          <Box>
            <StepTitle>{step.title}</StepTitle>
            <StepDescription>{step.description}</StepDescription>
          </Box>
    
          <StepSeparator />
        </Step>
      ))}
    </Stepper>

Patch Changes

@chakra-ui/[email protected]

Minor Changes

Patch Changes

@chakra-ui/[email protected]

Minor Changes

  • 379f347a8
    Thanks @segunadebayo! - Add support for
    aspectRatio style prop to enable the usage of the native aspect ratio
    property

  • #7494
    27dcf2f56
    Thanks @kuroppe1819! - Add support for
    nested semantic tokens in theme. It is now possible to declare semantic tokens
    by nesting objects.

    BEFORE:

    const theme = {
      semanticTokens: {
        colors: {
          "background.pressed.base": { default: "blue.800", _dark: "blue.300" },
          "background.pressed.subtle": { default: "blue.300", _dark: "blue.700" },
        },
      },
    }

    AFTER:

    const theme = {
      semanticTokens: {
        colors: {
          background: {
            pressed: {
              base: { default: "blue.800", _dark: "blue.300" },
              subtle: { default: "blue.300", _dark: "blue.700" },
            },
          },
        },
      },
    }

    This allows for cleaner grouping and organization of tokens.

  • #7502
    49a29a238
    Thanks @estheragbaje! - Add _horizontal
    and _vertical pseudo props to style orientation data attributes

@chakra-ui/[email protected]

Minor Changes

@chakra-ui/[email protected]

Minor Changes

@chakra-ui/[email protected]

Minor Changes

@chakra-ui/[email protected]

Minor Changes

  • #7494
    27dcf2f56
    Thanks @kuroppe1819! - Add support for
    nested semantic tokens in theme. It is now possible to declare semantic tokens
    by nesting objects.

    BEFORE:

    const theme = {
      semanticTokens: {
        colors: {
          "background.pressed.base": { default: "blue.800", _dark: "blue.300" },
          "background.pressed.subtle": { default: "blue.300", _dark: "blue.700" },
        },
      },
    }

    AFTER:

    const theme = {
      semanticTokens: {
        colors: {
          background: {
            pressed: {
              base: { default: "blue.800", _dark: "blue.300" },
              subtle: { default: "blue.300", _dark: "blue.700" },
            },
          },
        },
      },
    }

    This allows for cleaner grouping and organization of tokens.

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

@chakra-ui/[email protected]

Patch Changes

  • #7525
    d14458b5a
    Thanks @TylerAPfledderer! - Reverts the
    use of the baseTheme in the plugin

    With the added features of extendBaseTheme and ChakraBaseProvider, it was
    determined that the provider is considered unnecessary.

    Custom theming is to be expected for components when there are no defaults
    rendered.

    For Gatsby, this means that the plugin can be reverted back to it's original
    setup, and still be able to accept extendBaseTheme to reduce the payload of
    the component themes when customizing them.

@chakra-ui/[email protected]

Patch Changes

@vercel
Copy link

vercel bot commented Apr 3, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
chakra-ui-storybook ✅ Ready (Inspect) Visit Preview Apr 24, 2023 11:06pm

@segunadebayo segunadebayo merged commit 397c462 into main Apr 25, 2023
5 checks passed
@segunadebayo segunadebayo deleted the changeset-release/main branch April 25, 2023 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant