# Add "context" to types provided in Typed Input

**URL:** https://discourse.nodered.org/t/add-context-to-types-provided-in-typed-input/64109
**Category:** Feature Requests
**Created:** [18 June 2022 14:14 UTC](https://discourse.nodered.org/t/add-context-to-types-provided-in-typed-input/64109 "2022-06-18T14:14:47Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [6 April 2023 03:49 UTC](https://discourse.nodered.org/t/add-context-to-types-provided-in-typed-input/64109/19 "2023-04-06T03:49:02Z")

</div>

> [@knolleary](#):
>
> Whether we then add it to the list of types provided in the Change node can be debated.

I'm sure you remember our previous discussions of this, but for the benefit of newcomers, here are links to some of the posts:

> [@Local Context (revisited)](https://discourse.nodered.org/t/local-context-revisited/889/6):
>
> Reviving an old discussion. Has it been settled whether adding local context to the change node would be a good idea -- or even possible? I am working on a flow that uses function nodes where thechange node would be a better choice if it had this capability.

> [@\[Feature Request\]Let change nodes access local context](https://discourse.nodered.org/t/feature-request-let-change-nodes-access-local-context/29491):
>
> ...like function nodes, so they remember stuff from one message to the next instead of having to use flow or global storage

My view on this hasn't changed in the years since, but if there are good reasons not to add this feature, I would be happy to hear them.

---

_[View the full topic](https://discourse.nodered.org/t/add-context-to-types-provided-in-typed-input/64109)._