Viewing profile — brianvaughn

Thank you for elaborating.

Glad the tutorial is helpful! :) It was a last minute idea and I'm excited about how it turned out.

That's definitely not the intent.

It's a little scary to upload a completely new version, when you know there's that many weekly active users that are going to be hammering away on it soon.

> but Facebook is the last company I'd want to have the obscene privileges that extensions have. reply Sounds like you're talking about extensions in general , but for what it's wo…

You might still check out DevTools at some point :) They do a lot of small things that can be nice.

Doesn't sound like it. React DevTools uses the `postMessage` API to communicate, not websockets.

Sunil has also worked at Yahoo on maps.yahoo.com, specifically on tooling to manage styling.

> s everybody knows about the implicit context(s) that also affect component behavior. Just in case there's any misunderstanding- (I don't think there is, but just being safe)- con…

Yes, but then that prop would need to be passed down explicitly through every component. This would require a _lot_ of boilerplate.

> In your experience, what are the kind of things that people do in `componentWillMount` that they shouldn't be doing? The biggest one is probably adding event listeners or setting…

I'm not sure why you would need to upgrade your app in that case. Is the problem that our documentation only reflects the latest release?

Upgrading any project after 3 years of inactivity would be difficult, regardless of framework. I did not mean to imply that you would need to step through every minor version thoug…

> Well, I tend to make a lot of very small stateless components. If a component is 1-6 JSX tags, the new context API represents a boilerplate overhead of between 100 and ~17%. Not …

I'm curious why the theme example I mentioned in my earlier comment- (and showed in the docs)- doesn't qualify as "useful" to you. Another example would be using context to share t…

> I guess I should start using componentDidUpdate instead? Sounds like it, based on your description! > The other case of componentWillReceiveProps usage I see is where there is co…

Lifecycles aren't mandatory in React. Pure functional components don't use them. Stateful class components don't necessarily need them either (although they _can_ be useful, partic…

I don't think we know enough about where compilation will end up to comment much. I wouldn't expect TypeScript to be negatively affected though (since it compiles to JavaScript). S…

The `withTheme` HOC uses `createContext` and `forwardRef`. I don't think it's contrived. :) https://reactjs.org/blog/2018/03/29/react-v-16-3.html#forwar...

> From the outside, having seen Fiber slated for release in 16.0.0 and, being pushed back to an unknown 16.x release, and then being pushed back to 17.0.0, it seems like you had no…

> However, the amount of large internal changes indicates that as you improve and (most likely) shed unneeded complexity, that there must have been complexity to shed. The v16 rewr…

No, but you could do it in a similar way as the "Dynamic Context" example [1] - store the authenticated user/status in component `state` and pass it down via a AuthenticationContex…

Our upgrade process is very gradual. As long as you've fixed all of the dev warnings for the last minor release of a given version, you should be able to upgrade to the next major …

Would you elaborate on what you find clunky about the new context API? :)

The purpose of componentWillReceiveProps was to update state in response to props changes. (This is also the purpose of getDerivedStateFromProps.) What you're describing sounds mor…