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-v14] Use findDOMNode where needed and fix package #1859

Merged
merged 1 commit into from
Oct 14, 2015
Merged

[React-v14] Use findDOMNode where needed and fix package #1859

merged 1 commit into from
Oct 14, 2015

Conversation

oliviertassinari
Copy link
Member

  • Remove -rc1 with the offical release.
  • Use ^ instead of >= to prevent future breaking changes with react v0.15.
  • Remove deprecated getDOMNode.
  • Fix docs webpack-dev-server.

@oliviertassinari
Copy link
Member Author

Fix some of #1782

@@ -23,7 +23,7 @@ var config = {
},
//Modules will be searched for in these directories
modulesDirectories: [
"web_modules",
Copy link
Contributor

Choose a reason for hiding this comment

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

isn't it redundant with the line bellow?

Copy link
Member Author

Choose a reason for hiding this comment

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

Webpack fail for me without.

Copy link
Contributor

Choose a reason for hiding this comment

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

strange... all node_modules of the project are supposed to be included in a 'whatever the current directory is' manner just bellow..

Copy link
Member Author

Choose a reason for hiding this comment

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

Hum, with the default modulesDirectories yes. But I think that since we overide it, it's no longer true.

@shaurya947
Copy link
Contributor

Thanks @oliviertassinari

shaurya947 added a commit that referenced this pull request Oct 14, 2015
[React-v14] Use findDOMNode where needed and fix package
@shaurya947 shaurya947 merged commit 04fb97f into mui:react-0.14-support Oct 14, 2015
@@ -78,8 +79,8 @@ const CalendarYear = React.createClass({
_scrollToSelectedYear() {
if (this.refs.selectedYearButton === undefined) return;

let container = this.getDOMNode();
let yearButtonNode = this.refs.selectedYearButton.getDOMNode();
let container = this.findDOMNode();
Copy link
Member Author

Choose a reason for hiding this comment

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

should be ReactDOM.findDOMNode(this);
Fixed in #1882

@shaurya947
Copy link
Contributor

@oliviertassinari are you working on fixing these?

@oliviertassinari
Copy link
Member Author

@shaurya947 Yes here #1882.

@oliviertassinari oliviertassinari deleted the react-v14-fix-package branch November 3, 2015 10:51
@zannager zannager added the docs Improvements or additions to the documentation label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants