optimize useContext call

[mdynnl]

Summary

No benchmarks are ran as this should not need one. Feel free to do though 😂.

How did you test this change?

pnpm test

[changeset-bot]

⚠️ No Changeset found

Latest commit: 287acff

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coveralls]

Pull Request Test Coverage Report for Build 9997328613

Details

• 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.001%) to 93.561%

---

Totals
Change from base Build 9751531446:	0.001%
Covered Lines:	4187
Relevant Lines:	4409

---

💛 - Coveralls

[ryansolid]

Nice that saves 8 bytes minified and is probably a tiny bit faster

[maciek50322]

how about

Owner?.context?.[context.id] ?? context.defaultValue

[ryansolid]

I've been avoiding optional chaining as we don't transform JS in the repo and some platforms down't support optional chaining. We've had issue trying to introduce it in the past.