Skip to content

Conversation

@Sumei1009
Copy link

fixes #2887

},
};

ReactDOMDebugTool.addDevtool(ReactDOMUnknownPropertyDevtool);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are you removing the devtool? This appears to be going in the wrong/opposite direction.

null
);

warning(
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we want to use the “devtool” API for the new warnings. You can check how ReactDOMUnknownPropertyDevtool currently works for the context—it just needs to be called during the element creation.

@Sumei1009
Copy link
Author

I modified some method so that ReactDOMUnknownPropertyDevtool would be called on element creation. Is it the right way?

@facebook-github-bot
Copy link
Contributor

@Sumei1009 updated the pull request.

@gaearon
Copy link
Collaborator

gaearon commented Apr 11, 2016

Can you please rebase so it merges cleanly, and fix the lint issues? You can run npm run lint locally and see why ESLint is failing. Thanks!

@jimfb
Copy link
Contributor

jimfb commented Apr 13, 2016

Ping @Sumei1009

Sumei1009 pushed a commit to Sumei1009/react that referenced this pull request Apr 14, 2016
Sumei1009 pushed a commit to Sumei1009/react that referenced this pull request Apr 14, 2016
Sumei1009 pushed a commit to Sumei1009/react that referenced this pull request Apr 14, 2016
Sumei1009 pushed a commit to Sumei1009/react that referenced this pull request Apr 14, 2016
@Sumei1009 Sumei1009 closed this Apr 14, 2016
Sumei1009 pushed a commit to Sumei1009/react that referenced this pull request Apr 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Detect React DOM element with a wrong attribute name

4 participants