zero update propagation Context

(Documentation only) feature request

There is a set of cases, when you need to read context only once. Read without any future update, so no subscription is needed - mount effect are a great example of this.

Some libraries already using this pattern, for example sweet-state uses readContext(“a hack”) to just get the data from React, in a same “no update” mode.

I think this pattern should be documented, but it seems a bit wrong to use useContext to do so, as long as there are some expectations about how useContext is working.

What do you think about useUntrackedContextSelector? The same useContextSelector, but “untracked”?

[theKashey]

Probably you are right, and I could solve the problem by creating two context - one with propagation, and another without. At least I would be able to use only built-in React functions. Or readContext hack.

[dai-shi]

I understand your point. (I glanced react-sweet-state code using readContext before and I saw @JoviDeCroock 's code using React.useContext for that purpose.)

My preference is something like useReadContext. (no selector)

export const useReadContext = React.useContext;

However, I’m not sure if it should be a stable feature, because even if @gnoff 's RFC is accepted, this feature is not provided. (correct?) What do you think?