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

It's just doesn't work. #1303

Closed
milworm opened this issue Jul 31, 2015 · 3 comments
Closed

It's just doesn't work. #1303

milworm opened this issue Jul 31, 2015 · 3 comments
Labels
core Infrastructure work going on behind the scenes

Comments

@milworm
Copy link

milworm commented Jul 31, 2015

Hi,

I've tried to use your library, but it just doesn't work :(
I have this code:
https://gist.github.com/milworm/f3ee2eb372b5049e4ec7

which is super simple, but it produces this error (even tried to use different versions: 0.13.3, 0.14-beta):
https://gist.github.com/milworm/4f80189a4554f69fea85

I've just switched to old 0.12 and I now I am able to render components, but now when I click on button it raises this error:
Uncaught TypeError: React.findDOMNode is not a function

which is understandable because React.findDOMNode was introduced in 0.13.
So, the conclusion is:
material-ui doesn't work with reactjs (0.13 or 0.14).

Thanks.

@m-ret
Copy link

m-ret commented Jul 31, 2015

Create a file only for this. I just got it working

import React from 'react';
import { RouteHandler, Link } from 'react-router';
import { Styles } from 'material-ui';
import injectTapEventPlugin from 'react-tap-event-plugin';

// Stylesheets.
import style from './style.scss';

const ThemeManager = new Styles.ThemeManager();

injectTapEventPlugin();

export default class App extends React.Component { 

  static childContextTypes = {
    muiTheme : React.PropTypes.object
  }

  getChildContext () {
    return {
      muiTheme : ThemeManager.getCurrentTheme()
    };
  }

  render () {
    return <RouteHandler />;
  }

}

@milworm
Copy link
Author

milworm commented Aug 1, 2015

Sorry, my bad.. I think it was a problem with jspm. Basically when I use
jspm install npm:material-ui

for some very strange reason in my config.js - file I have:

    "npm:material-ui@0.10.2": {
      "classnames": "npm:classnames@1.2.2",
      "process": "github:jspm/nodelibs-process@0.1.1",
      "react": "npm:react@0.12.2", // 0.12.2 WHICH IS WRONG, AS IT SHOULD BE 0.13.3
      "react-draggable2": "npm:react-draggable2@0.5.1",
      "react-tap-event-plugin": "npm:react-tap-event-plugin@0.1.7"
    },

and after I changed it from 0.12.2 to 0.13.3 it works :(

@milworm milworm closed this as completed Aug 1, 2015
@kwo
Copy link

kwo commented Aug 31, 2015

same thing here, just do this

jspm install npm:material-ui
jspm resolve --only npm:react@0.13.3
jspm clean

mnajdova pushed a commit to mnajdova/material-ui that referenced this issue Nov 10, 2020
* Implement forwardingRef, closes, mui#1303

* Try to fix test failures on CI

* Fix ref forwarding test

* Fix eslint error

* Add yarn prettier script
@oliviertassinari oliviertassinari added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Dec 25, 2022
@zannager zannager added core Infrastructure work going on behind the scenes and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Development

No branches or pull requests

5 participants