fix: show color hex value as swatch title

[braaar]

get color value using getColor from @theme-ui/color instead of get from theme-ui.

fixes #2112

See the issue for more details

Version

Published prerelease version: v0.15.0-develop.29

Changelog

🎉 This release contains work from new contributors! 🎉

Thanks for all your work!

❤️ Luke Watts (@thisislawatts)

❤️ Valto Savi (@pointlessrapunzel)

Release Notes

Pull out MDX to be opt-in (#2288)

Breaking: theme-ui no longer includes @theme-ui/mdx — MDX is now opt-in.

If your project is not using MDX or importing Themed, you shouldn't need to
change anything.

• MDXProvider is no longer included in Theme UI ThemeProvider, and has been
  removed in favour of an useThemedStylesWithMdx hook.

  • Migration: Use useThemedStylesWithMdx together with MDXProvider and useMDXComponents from @mdx-js/react.

    import {
      MDXProvider,
      useMDXComponents,
      Components as MDXComponents,
      MergeComponents as MergeMDXComponents,
    } from '@mdx-js/react'
    import { useThemedStylesWithMdx } from '@theme-ui/mdx'
    import { ThemeProvider, Theme } from 'theme-ui'
    
    interface MyProviderProps {
      theme: Theme
      components?: MDXComponents | MergeMDXComponents
      children: React.ReactNode
    }
    function MyProvider({ theme, components, children }: MyProviderProps) {
      const componentsWithStyles = useThemedStylesWithMdx(useMDXComponents(components))
    
      return (
        <ThemeProvider theme={theme}>
          <MDXProvider components={componentsWithStyles}>
            {children}
          </MDXProvider>
        </ThemeProvider>
      )
    }

• Themed components dict and other exports from @theme-ui/mdx are no longer reexported from theme-ui.

  • Migration: Import it from @theme-ui/mdx instead.

    -  import { Themed } from 'theme-ui'
    +  import { Themed } from '@theme-ui/mdx'

Remove @theme-ui/editor (#2292)

• Breaking: @theme-ui/editor was removed. Use CSS GUI instead.
  • /customize page in Theme UI docs has been removed. Use Components.ai Theme Builder or an alternative instead.

Drop support for React 16 + 17 (#2215)

Theme UI 0.15.0 drops support for React 16 and React 17. Your use case may still work, but we don't guarantee it.

---

🚀 Enhancement

• Pull out MDX to be opt-in #2288 (@hasparus @beerose @lachlanjc hasparus@Piotrs-MacBook.local)
• Drop support for React 16 + 17 #2215 (@hasparus)

🐛 Bug Fix

• fix(e2e): add force=true to a test (@hasparus)
• fix: fix release workflow (empty commit) (@hasparus)
• Remove @theme-ui/editor #2292 (@hasparus)
• fix(mdx): add .sx props to Themed.X styles #2250 (@hasparus)

👨‍💻 Minor changes

• Specify MDX React version (@hasparus)

🏠 Internal

• docs: Update Contributing doc with pnpm info #2320 (@lachlanjc @hasparus)
• prism: Fix crash when className prop is missing #2322 (@lachlanjc)
• Docs: Group project templates by framework, add Remix #2276 (@lachlanjc)
• docs: re-order sidebar components into alphabetical order #2232 (@thisislawatts)
• docs: Specify MDX React version #2233 (@pointlessrapunzel)

Authors: 7

• Aleksandra (@beerose)
• Brage Sekse Aarset (@braaar)
• Lachlan Campbell (@lachlanjc)
• Luke Watts (@thisislawatts)
• Piotr (hasparus@Piotrs-MacBook.local)
• Piotr Monwid-Olechnowicz (@hasparus)
• Valto Savi (@pointlessrapunzel)

[vercel]

@braaar is attempting to deploy a commit to the Theme UI Team on Vercel.

A member of the Team first needs to authorize it.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit c1e4f7f:

Sandbox	Source
next-theme-ui-example	Configuration
gatsby-plugin-theme-ui-example	Configuration

[lachlanjc]

Code lgtm!

[hasparus]

Nice catch!

You updated the package.json, and to pass the installation with frozen lockfile on CI, you'll need to run pnpm install and then commit the pnpm-lock.yaml. I tried to do this for you, but I can't push to your develop :P

[braaar]

Nice catch!

You updated the package.json, and to pass the installation with frozen lockfile on CI, you'll need to run pnpm install and then commit the pnpm-lock.yaml. I tried to do this for you, but I can't push to your develop :P

I'll get on it

[braaar]

I'm not getting a new lockfile when running pnpm install. Should I delete the old one first? I tried running it at root and in packages/style-guide.

[braaar]

I invited you as a collaborator on my fork, @hasparus 🤷

[hasparus]

I invited you as a collaborator on my fork, @hasparus 🤷

Thanks! For the future — There should be a checkbox somewhere in the PR called "Allow edits from maintainers", so you don't need to add everybody as collaborators.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

Edit: That might have been a problem on my side.

[vercel]

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

Name	Status	Preview	Updated
theme-ui	✅ Ready (Inspect)	Visit Preview	Sep 20, 2022 at 11:40AM (UTC)