You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
render(){// As per documentation, unset date in uncontrolled mode be [null, null]// http://blueprintjs.com/docs/#datetime/daterangeinput// tslint:disable-next-line:no-anyconstvalue: [Date|undefined,Date|undefined]=[this.props.from.value ? this.props.from.value : undefined,this.props.to.value ? this.props.to.value : undefined];return(<BlueprintDate.DateRangeInputonChange={this.onChange}value={value}/>);
Actual behavior
The type definition requires value to be of the type [Date | undefined, Date | undefined]. Passing [undefined, undefined], however, results in the following:
Expected behavior
I expect this to produce the same behavior as [null, null], which is, as of now, disallowed by the type signature.
The text was updated successfully, but these errors were encountered:
Bug report
Steps to reproduce
Actual behavior
The type definition requires
value
to be of the type[Date | undefined, Date | undefined]
. Passing [undefined, undefined], however, results in the following:Expected behavior
I expect this to produce the same behavior as
[null, null]
, which is, as of now, disallowed by the type signature.The text was updated successfully, but these errors were encountered: