Add custom hook for context to avoid assertions

[filiptammergard]

I'd like to avoid adding assertions and excessive undefined/null checks. I generally use this approach and I think it can be considered a pretty widely spread good practice.

[eps1lon]

Definitely agree.

I would elaborate on different patterns though (don't we already have such a section?):

• runtime type checks
• static type assertions

[filiptammergard]

Hey @eps1lon! I gave reworking the entire context page a try. I think the page is containing way too many not recommended patterns and unpractical examples that don't belong in the basic cheatsheet. I think providing recommended patterns for some common use cases together with some alternative patterns is a better approach. Patterns like context getters might fit in the advanced cheatsheet, but they would still require some rework.

The suggested page is based on examples and recommendations from the new React docs.

What do you think?

[eps1lon]

Let's not do this for now. There are instances where type assertions are better (since they have no runtime impact) but it's on a case-by-case basis.

The rest is perfect. Nice job 👍🏻

[filiptammergard]

Do you mean let's remove the "(not recommended)" part?

[eps1lon]

Yeah. Though I think we should help somewhat in guiding. So maybe downgrade it from the heading to a paragraph like "when you don't know which to chose, use runtime checking and throwing".

[filiptammergard]

Added this in the end now:

When you don't know what to choose, prefer runtime checking and throwing over type asserting.