Re:How I learned to stop worrying and love React
by ble on Saturday May 16, 2015 @09:04AM
(#9555938)
You want to look at the DOM structure of the page as it exists in the loaded page and have I got a treat for you! Figure out how to open the web inspector for your browser; the keyboard shortcuts are ctrl-shift-I or cmd-shift-I or cmd-opt-I on a few (platform, browser) pairs.
(This will show you the actual DOM, not the React components... but since you were talking about 'view-source', this might help you too.)
Re:How I learned to stop worrying and love React
by hirsin on Saturday May 16, 2015 @12:22PM
(#9556647)
Or hit F12, works in every browser and platform as long as the key is present.
Re:How I learned to stop worrying and love React
by hobby_body on Sunday May 17, 2015 @03:27AM
(#9559067)
Between Firefox, Chrome, and Safari on OSX, it only does anything in Firefox (toggles Firebug).
Re:How I learned to stop worrying and love React
by fensipens on Saturday May 16, 2015 @09:24AM
(#9556002)
Thanks, that's what I've been looking for!
You're welcome!
Using the web inspector has been such a massive and continuous boost to my learning/work with webpages and I'm extremely glad to share it with someone it might help.
Re:How I learned to stop worrying and love React
by jawns on Saturday May 16, 2015 @08:29AM
(#9555848)
In Chrome, there's a cool React dev tools extension that shows you the React components.
https://chrome.google.com/webstore/detail/react-developer-to...
Re:How I learned to stop worrying and love React
by hcarvalhoalves on Saturday May 16, 2015 @11:12AM
(#9556365)
That's actually better than looking at the HTML output, unless you're debugging something really weird. With React you should treat HTML as an implementation detail and work in terms of component trees.
Good point; How does one view the resulting react-page anyway? CTRL+U shows <body><script.../></body> no matter what state the SPA is in..