[Feature Request] Defining valid time range within duckling plugin itself

[souravkgoyal]

Quoted the problem below that we face if we don't have a valid time range defined.
For कल 12:00 बजे duckling gives me
[
{
"body": "कल 12:00 बजे",
"start": 0,
"value": {
"values": [
{
"value": "2022-03-05T00:00:00.000+05:30",
"grain": "minute",
"type": "value"
},
{
"value": "2022-03-05T12:00:00.000+05:30",
"grain": "minute",
"type": "value"
}
],
"value": "2022-03-05T00:00:00.000+05:30",
"grain": "minute",
"type": "value"
},
"end": 12,
"dim": "time",
"latent": false
}
]
Now here the right value to capture would be 2022-03-05T12:00:00.000+05:30 but the duckling plugin chooses 2022-03-05T00:00:00.000+05:30 from
[
{
"value": "2022-03-05T00:00:00.000+05:30",
"grain": "minute",
"type": "value"
},
{
"value": "2022-03-05T12:00:00.000+05:30",
"grain": "minute",
"type": "value"
}
],
so how can I make it capture 2022-03-05T12:00:00.000+05:30? and for similar cases make sure that we will be only taking the values not coming in midnight
"value":"2022-03-05T03:00:00.000+05:30","grain":"hour","type":"value"},"end":5,"dim":"time","latent":false}]
Wrote a custom mutator here to tackle this problem.