Not sure that this is the right place to put WebEditUserAvatarProvider in the React component tree.

Here's my understanding:

• On native, we have most of our providers in Root() at "the top level" of the application.

• On web, we have (fewer) providers wrapping {content} in App():

as well as some that are more "local" to the components from where they're consumed, eg:

• It's generally considered good for performance to "push providers down" to limit scope and reduce re-renders.

• However, in this situation I think it makes sense to have WebEditUserAvatarProvider "as high as possible" because we may consume it in other parts of the application (eg if the user avatar is shown anywhere else on the page in the future and we want a spinner to indicate that it's changing or whatever).

• Since content in app.react.js depends on loggedIn, I think it makes sense to have the provider "within" this.renderMainContent()... since that's where a UserAvatar is relevant anyways:

• Within this.renderMainContent(), it makes sense to wrap header (maybe we show user avatar in header one day?), mainContent, and maybe CommunityPicker within the provider.

So I thought it made sense to wrap what's returned by this.renderMainContent() with the provider. However, that doesn't feel right. I would expect something more like native where the provider is included within a deeply nested "triangle" of providers.

Any suggestions on a more appropriate place to include this provider or some other way I should be thinking about this?

Yeah, will update