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

Export SerializedStyles from @emotion/react flow types #2206

Merged
merged 2 commits into from
Jan 9, 2021

Conversation

jimmydief
Copy link
Contributor

What: Export SerializedStyles from @emotion/react flow types

Why: This will make it easier to properly type the return value of the css function in Flow.

How: Re-exporting the type.

Checklist:

  • Documentation (N/A?)
  • Tests (N/A?)
  • Code complete
  • Changeset

Fixes #2203

This will make it easier to properly type the return value of the `css` function in Flow.
@changeset-bot
Copy link

changeset-bot bot commented Jan 8, 2021

🦋 Changeset detected

Latest commit: 6e91f09

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@emotion/react Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jan 8, 2021

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 6e91f09:

Sandbox Source
Emotion Configuration

@Andarist Andarist merged commit 4d2e732 into emotion-js:master Jan 9, 2021
@Andarist
Copy link
Member

Andarist commented Jan 9, 2021

Thanks!

@github-actions github-actions bot mentioned this pull request Jan 9, 2021
@jimmydief jimmydief deleted the add_serialized_styles_type branch January 10, 2021 20:24
facebook-github-bot referenced this pull request in facebook/flipper Mar 23, 2021
Summary:
Bumps [emotion/styled](https://github.com/emotion-js/emotion) from 11.0.0 to 11.1.5.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/emotion-js/emotion/releases"><code>@​emotion/styled's releases</code></a>.</em></p>
<blockquote>
<h2>emotion/[email protected]</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://github.com/emotion-js/emotion/commit/d0293508016dc07c5ad502b9eb0bec99ede1d37b"><code>d0293508</code></a> <a href="https://github.com/emotion-js/emotion/pull/2240">#2240</a> Thanks <a href="https://github.com/wolszczak96"><code>@​wolszczak96</code></a>! - <code>as</code> prop has been removed from TypeScript declarations for composite components. This prop has not actually been handled by default by <code>styled</code> for those components - to make <code>styled</code> handle it you need to provide a custom <code>shouldForwardProp</code> that doesn't forward the <code>as</code> prop.</p>
</li>
<li>
<p>Updated dependencies [<a href="https://github.com/emotion-js/emotion/commit/f3c2e81d10b63811ebbc6c5b11fa3553a2605f44"><code>f3c2e81d</code></a>]:</p>
<ul>
<li>emotion/[email protected]</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/emotion-js/emotion/commit/2fe9e0e945be8a933521a96c2a242c5b397aa846"><code>2fe9e0e</code></a> Version Packages (<a href="https://github.com/emotion-js/emotion/issues/2207">#2207</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/d0293508016dc07c5ad502b9eb0bec99ede1d37b"><code>d029350</code></a> Removed type for <code>as</code> prop for composite components (<a href="https://github.com/emotion-js/emotion/issues/2240">#2240</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/f3c2e81d10b63811ebbc6c5b11fa3553a2605f44"><code>f3c2e81</code></a> Added <code>option</code> &amp; <code>fallback</code> AMP props to the list of valid props (<a href="https://github.com/emotion-js/emotion/issues/2232">#2232</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/b62647e8f52c9646d7f4f6eb789db1b84c94228a"><code>b62647e</code></a> Fix regex to comply with no-useless-escape ESLint rule</li>
<li><a href="https://github.com/emotion-js/emotion/commit/400c6f72905a4676f852b09405421a7ca8d7a3a2"><code>400c6f7</code></a> Update slack link</li>
<li><a href="https://github.com/emotion-js/emotion/commit/00cb6141a74f374efb8a01218e4518ce691f1723"><code>00cb614</code></a> Update example describing how one can provide a library theme type using inte...</li>
<li><a href="https://github.com/emotion-js/emotion/commit/4d2e732e9f0c8385c77c7bc43d4ccea7b30b9d37"><code>4d2e732</code></a> Added export for <code>SerializedStyles</code> Flow type from <code>emotion/react</code> (<a href="https://github.com/emotion-js/emotion/issues/2206">#2206</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/a89d4257b0246a1640a99f77838e5edad4ec4386"><code>a89d425</code></a> Lift Emotion 11 codemod instructions to the earlier spot in the docs (<a href="https://github.com/emotion-js/emotion/issues/2194">#2194</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/a1e44aa56b1c54ec20aa9e49cfa76fa74583ba81"><code>a1e44aa</code></a> Version Packages (<a href="https://github.com/emotion-js/emotion/issues/2187">#2187</a>)</li>
<li><a href="https://github.com/emotion-js/emotion/commit/71ca9be3368ddb0a95ef5b2db7a97c67ab440593"><code>71ca9be</code></a> Fix TypeScript support for custom components with non-standard declarations (...</li>
<li>Additional commits viewable in <a href="https://github.com/emotion-js/emotion/compare/emotion/[email protected]...@emotion/[email protected]">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@emotion/styled&package-manager=npm_and_yarn&previous-version=11.0.0&new-version=11.1.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

 ---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `dependabot rebase` will rebase this PR
- `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `dependabot merge` will merge this PR after your CI passes on it
- `dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `dependabot cancel merge` will cancel a previously requested merge and block automerging
- `dependabot reopen` will reopen this PR if it is closed
- `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Pull Request resolved: #2067

Reviewed By: passy

Differential Revision: D27230129

Pulled By: priteshrnandgaonkar

fbshipit-source-id: fcd95fb0db6b160df165189b6841ce5a42694459
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.

Include SerializedStyles in @emotion/react's flow types
2 participants