Bug with Range Picker Component (Nebular v5.0.0)
See original GitHub issueIssue type
I’m submitting a … (check one with “x”)
- bug report
- feature request
Issue description
Current behavior:
If you select a range and then you try to select another range from another month, you get this error: t.getFullYear is not a function
and months of the year are not shown.
Expected behavior:
Months of the year should be shown when I try to select another range.
Steps to reproduce:

Other information:
Tested with Google Chrome v80.0.3987.149 and Nebular v5.0.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Datepicker Angular UI Component - Nebular - GitHub Pages
Chooses datepicker adapter based on passed picker component. filterValidator() ... Emits range when start selected and emits again when end selected.
Read more >Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
Bug :128538 - "sys-apps/coreutils: /bin/hostname should be installed from coreutils not sys-apps/net-tools" status:UNCONFIRMED resolution: severity:enhancement ...
Read more >Web Libraries in Jars - WebJars
Bootstrap Date Range Picker, org.webjars, bootstrap-daterangepicker ... org.webjars.bower, github-com-toddmotto-angular-component, 0.0.7.
Read more >Source - GitHub
API changes - `@nebular/theme/styles/_components.scss` file removed. ... **range-picker:** correct type for min, max, filter properties ...
Read more >Changelog - Lansweeper.com
10.3.0.0, LsPush 8.4.100.1, LsAgent Windows 10.0.1.1, SQL 600 (17 Nov 2022) ... Fixed: LAN-12993 During SSDP discovery of an IP range scan, excessive...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have managed to find a workaround while this gets fixed. You can put this in your AppModule constructor to overwrite the wrong part:
In the original the this.selectedValue is passed in the second parameter which is the range. This works for me, hope it helps.
The issue was fixed by #2330 (part of the
6.1.0
release). The problem was thatNbCalendarRangeComponent
was usingNbCalendarMonthCellComponent
as cell component instead ofNbCalendarRangeDayCellComponent
. After the update to the fixed version, you can remove lines with patchingNbCalendarMonthCellComponent.prototype
as it would break regular picker.