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

Give the user a warning when using unoptimized JSX code #359

Merged
merged 3 commits into from
Sep 19, 2013
Merged

Give the user a warning when using unoptimized JSX code #359

merged 3 commits into from
Sep 19, 2013

Conversation

SanderSpies
Copy link
Contributor

As discussed in: https://groups.google.com/forum/#!topic/reactjs/5anr4Oxs8tA

Implemented it for all the situations whereby text/jsx is used - not just synchronous loading as discussed in the group conversation.

@jordwalke
Copy link
Contributor

Yeah - can you imagine if people thought it was okay to compile JSX inside of the browser! Awesome. Not sure the markdown anchor belongs in this PR though?

@@ -20,7 +20,7 @@ We provide CDN-hosted versions of React [on our download page](/react/downloads.

We have instructions for building from `master` [in our GitHub repository](https://github.com/facebook/react). We build a tree of CommonJS modules under `build/modules` which you can drop into any environment or packaging tool that supports CommonJS.

## JSX
## <a id="jsx"></a>JSX
Copy link
Member

Choose a reason for hiding this comment

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

Like @jordwalke said, I'm going to figure this out in a separate diff. But good call.

…ct this to be done by @zpao's pull request)

- removed the if statement and now always provide a warning message (as proposed by @spicyj)
- improved the warning message
@zpao
Copy link
Member

zpao commented Sep 19, 2013

💥 Thanks!

zpao added a commit that referenced this pull request Sep 19, 2013
Give the user a warning when using unoptimized JSX code
@zpao zpao merged commit 8875e1d into facebook:master Sep 19, 2013
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.

4 participants