# Introducing typed inputs in my first custom node ever
**URL:** https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658
**Category:** Developing Nodes
**Created:** [13 February 2020 15:24 UTC](https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658 "2020-02-13T15:24:59Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [13 February 2020 15:24 UTC](https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658/1 "2020-02-13T15:24:59Z")
Hi folks,
A couple of years ago I developed my first custom node ([node-red-contrib-msg-resend](https://github.com/bartbutenaers/node-red-contrib-msg-resend)), which a couple of numeric inputs on the config screen:
Both numeric values can be set dynamically via the input message (`msg.resend_interval` and `msg.resend_max_count`). This means that the config screen input contains the _default values_ _ **AND** _ these values can dynamically be overwritten via the input message.
Now I would like to allow the user to choose which msg field he wants to use (e.g. `msg.payload.interval`), instead of forcing him to use the `msg.resend_xxxx` fields.
This means I have to use typed inputs like this:
But then the interval is specified on the config screen _ **OR** _ in the input message.
So that would break existing flows...
Anybody has an idea how I can accomplish this?
Thanks !!
Bart
---
### Author:  [@michaelblight](https://discourse.nodered.org/u/michaelblight)
#### Post date: [14 February 2020 00:14 UTC](https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658/2 "2020-02-14T00:14:24Z")
Is it just a matter of sequencing the priorities? - use `msg.` if set; if not, use `msg.resend_interval` if present; if not, use number.
Assuming you have an input along the lines of:
```auto
```
Then the logic would be something like:
```auto
if (intervalType === 'msg') {
await RED.util.evaluateNodeProperty(...
} else if (msg.hasOwnProperty('resend_interval') {
...overridden from msg
} else if (intervalType === 'number') {
...use number entered
} else {
...confused now
}
```
For this to work for existing code, I expect you would have to default `intervalType` to 'number'.
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [14 February 2020 16:57 UTC](https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658/3 "2020-02-14T16:57:57Z")
> [@michaelblight](#):
>
> Is it just a matter of sequencing the priorities?
Hi Michael,
Thanks for the assistance! Yes indeed, but in the early days I thought that the config screen contained the default values, which could be overwritten by a control message. But with the typedinput (containing an "msg" and a "num" option), which one of both you want ...
But at first sight your code snippet indeed should work. Will have to mention in my readme that the `resend_xxx` input message fields are read for legacy reasons ...
Thanks a lot!!
Bart
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [14 April 2020 16:57 UTC](https://discourse.nodered.org/t/introducing-typed-inputs-in-my-first-custom-node-ever/21658/4 "2020-04-14T16:57:57Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.