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

Use emotion-next in the site, update to gatsby v2 and add Community page #720

Merged
merged 32 commits into from
Jun 28, 2018

Conversation

emmatown
Copy link
Member

What:
Use emotion-next in the site, update to gatsby v2 and add Community page

Why:
I wanted to see what the migration to emotion@10 will be like

How:

Checklist:

  • Documentation
  • Tests
  • Code complete

This isn't ready yet, I just wanted to open the PR to get people's thoughts on the Community page

import createBroadcast from './create-broadcast'
import { channel, contextTypes, type Theme } from './utils'

const isPlainObject = test =>
Object.prototype.toString.call(test) === '[object Object]'

type Props = {
theme: Theme
theme: Theme,
children?: ReactNode
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be optional? i get that it's technically possible to use it without children but it also doesn't make sense

@emmatown emmatown merged commit 4a95e71 into master Jun 28, 2018
@emmatown emmatown deleted the migrate-site-to-next branch June 28, 2018 08:38
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.

3 participants