Since when does Reason have JSX?
What should go into JSX 2.0?
11–20 of 102 posts
Re: What should go into JSX 2.0?
#12Earlier quoted context omitted.
How about ? Because that should already work, no?
You'd have to spread in the object, right?
I know, but it's too verbose for me.
BTW there is a discussion about this: https://github.com/facebook/jsx/issues/23
Re: What should go into JSX 2.0?
#13Since when does Reason have JSX?
JSX is actually a generic transformation of XML like structures to function calls. Since it's mostly used with React, that's the default, but you can use any function you like. It's the "pragma" option in the config for the plugin.
Re: What should go into JSX 2.0?
#14"What should go into JSX 2.0?" would be a much clearer title outside of the context of the GitHub issue.
Yup, even the issues not marked controversial seem so to me. I think JSX is quite nice but it has its limits/annoyances. One is obviously that it's not real HTML5. I would like to see a successor that is more like HTML5 without the X. No idea how that could be realized though... ;)
Sorry, what do you mean by this? (For those unfamiliar with the deviations)
Re: What should go into JSX 2.0?
#15I'd like a good system for conditional child components. I liked Flex's system.
Re: What should go into JSX 2.0?
#16I like how the if proposal is down voted, probably because it's mentioning Angular. Conditional rendering in React is not always very clean. Most codebases end up resorting with something similar to this in a container to show a spinner while data is loading and rendering it when done.
Problem is that the inner component will still be parsed and fail with cannot read property person of undefined. Yes, you can do this with a simple condition in your render function, but then it's not declarative any more.
Re: What should go into JSX 2.0?
#17I like how the if proposal is down voted, probably because it's mentioning Angular. Conditional rendering in React is not always very clean. Most codebases end up resorting with something similar to this in a container to show a spinner while data is loading and rendering it when done. Problem is that the inner component will still be parsed and fail with cannot read property person of undefined. Yes, you can do this…
How about { data && } ?
Re: What should go into JSX 2.0?
#18I like how the if proposal is down voted, probably because it's mentioning Angular. Conditional rendering in React is not always very clean. Most codebases end up resorting with something similar to this in a container to show a spinner while data is loading and rendering it when done. Problem is that the inner component will still be parsed and fail with cannot read property person of undefined. Yes, you can do this…
[deleted]
Re: What should go into JSX 2.0?
#19Re: What should go into JSX 2.0?
#20make it s-exp?