overriding request.context

[pi0]

Users might direclty update request.context in upgrade hook which is a wrong usecase.

Two possible solution:

• hydrate request.context (reference) after calling hook (more hackable / if non object value assigned makes things bad)
• make it a ready only getter (developers know they can't override)

---

          Thanks @sandros94, this gave me some much needed guidance! However, I found that setting the context to an object doesn't work, you have to set specific properties. For example (using `[email protected]`):

Trying to set request.context to a new object:

upgrade(request) {
  request.context = { data: 'test'}
},
open(peer) {
  console.log(peer.context) // logs {}
}

Setting a specific property in request.context:

upgrade(request) {
  request.context.data = 'test'
},
open(peer) {
  console.log(peer.context) // logs { data: 'test' }
}

Originally posted by @travis-r6s in #112 (comment)