Assign `tabId` to middleware request, if provided (#7695)
The `tabId` of the message sender is now added to the middleware request object. This step is omitted if the `tabId` is not provided. This is done early in the middleware stack, so the `tabId` should be available for any subsequent middleware to use. The Onboarding Middleware has also been modified to get the `tabId` from the request object, rather than expecting it as a parameter upon creation. This refactor will enable further uses of the `tabId`.feature/default_network_editable
parent
ef98e876a7
commit
1d2c57a2f3
@ -0,0 +1,14 @@ |
|||||||
|
|
||||||
|
module.exports = createTabIdMiddleware |
||||||
|
|
||||||
|
/** |
||||||
|
* Returns a middleware that appends the DApp TabId to the request |
||||||
|
* @param {{ tabId: number }} opts - The middleware options |
||||||
|
* @returns {Function} |
||||||
|
*/ |
||||||
|
function createTabIdMiddleware (opts) { |
||||||
|
return function tabIdMiddleware (/** @type {any} */ req, /** @type {any} */ _, /** @type {Function} */ next) { |
||||||
|
req.tabId = opts.tabId |
||||||
|
next() |
||||||
|
} |
||||||
|
} |
Loading…
Reference in new issue