Reed Harmeyer

> as someone unfamiliar with your idea of "hoisting", the first example doesn't really make it clear why we couldn't just stick the expanded-state into a regular context: > >...

Thank you for all your feedback, it's tremendously helpful and I'm definitely going to be making some revisions. There are answers/reasons to all these points so I just need to...

> if you suddenly want/need to add an unrelated context around a component, you can't -- that would break the hoisting! Nope, only the relevant contexts matter! Adding another context...

> (and if you go for the "innermost" one, it'd still have the "oops adding new contexts might break things" issue i mentioned before) Definitely inner-most, but I don't quite...

Thanks for taking the time to come up with this example! Yes, you're completely correct. This API isn't a breaking change but it does retcon how we think about Context...

For feature readers, everything above this comment was for an older version of the RFC where there was no `createScope`. Instead the scope was determined by what Contexts were used....

@bowheart thanks for your comment! I'll try and answer your questions. FYI there is an (old) sandbox in the post and the "Product Page" example is the real-world use case...