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

[react] Upgrade to React@15.5.3 #6543

Merged
merged 1 commit into from Apr 8, 2017
Merged

[react] Upgrade to React@15.5.3 #6543

merged 1 commit into from Apr 8, 2017

Conversation

oliviertassinari
Copy link
Member

@oliviertassinari oliviertassinari commented Apr 8, 2017

  • PR has tests / docs demo, and is linted.
  • Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
  • Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Limitations:

Related to #6542

@muibot muibot added PR: needs revision The pull request can't be merged. More details is available on the code review or fails in the CI and removed PR: Needs Review labels Apr 8, 2017
@@ -1,4 +1,5 @@
import React from 'react';
import PropTypes from 'prop-types';
Copy link
Member

Choose a reason for hiding this comment

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

These files don't need prop-types

Copy link
Member Author

Choose a reason for hiding this comment

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

Indeed, I'm on it :).

package.json Outdated
@@ -46,6 +46,7 @@
"publish": "npm run build && cd build && npm publish --tag next"
},
"peerDependencies": {
"prop-types": "^15.0.0",
Copy link
Member

Choose a reason for hiding this comment

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

prop-types won't conflict. Adding it to peer dependencies will further complicate installs. Many won't use prop-types. Like some typescript users (me included 😁). Just add it to normal dependencies. fewer missing peer dependency warns and fewer breakage to take care of.

@mbrookes
Copy link
Member

mbrookes commented Apr 8, 2017

image

❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉 ❤️ 🎉

@@ -3,7 +3,8 @@
import { create } from 'jss';
import jssPreset from 'jss-preset-default';
import { createStyleManager } from 'jss-theme-reactor';
import { PropTypes } from 'react';
import 'react';
Copy link
Member

Choose a reason for hiding this comment

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

😱 😱 codemod failure 😆

@@ -2,7 +2,8 @@
/* eslint-disable import/no-mutable-exports*/
/* eslint-disable flowtype/require-valid-file-annotation */

import { PropTypes } from 'react';
import 'react';
Copy link
Member

Choose a reason for hiding this comment

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

same

@oliviertassinari oliviertassinari added PR: Review Accepted and removed PR: Needs Review PR: needs revision The pull request can't be merged. More details is available on the code review or fails in the CI labels Apr 8, 2017
@oliviertassinari
Copy link
Member Author

I'm merging early. We have to start somewhere and other PR will most likely have to rebase.

@oliviertassinari oliviertassinari merged commit 4132bee into mui:next Apr 8, 2017
@oliviertassinari oliviertassinari deleted the next-react branch April 8, 2017 23:04
@muibot muibot added the PR: needs revision The pull request can't be merged. More details is available on the code review or fails in the CI label Apr 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: needs revision The pull request can't be merged. More details is available on the code review or fails in the CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants