fetrarij
Poll for future of ngx-daterangepicker-material
Hello all,
As you noticed, the version 10 of angular/material has now a daterange picker with, but recently with version 9 we released the version 3 of ngx-daterangepicker-materia wich depends on angular/material so my question is now, with theses options bellow, what do you recommend and why ?
1- "Keep current version (v3) which depends on angular/material" 2- "revive v2 (make it work with angular 10) which is enterely independant and you can customise your style" 3- "let the component die we wont need it anymore" 4- "other recommendation?"
@dmpasilva @praveenpuglia @MichielMag @angelo510 @steveacalabro @veerritu @Timebutt @mateusmcordeiro @styopdev @kirankumarsripati @duxor @butterknight @batgos @XHotSniperX @yousefkhan @sampath3797 @kodevtech @kgalanop @dwjohnston hello, could you participate? thanks in advance
Hey Fetraji,
The DateRange picker of angular/material actually differs from ngx-daterangepicker as it has no time selection. My choice would actually be number 2, to revive v2. We don't use any material styling and I've customised the style completely to be integrated with our application.
That being said, v3 is probably still a nice alternative for people who do wish for material styling as it has a timepicker which angular/material doesn't.
Hi @fetrarij ,
We previously used ng2-daterangepicker which uses jquery & https://www.daterangepicker.com/ library. Also, it doesn't work well with forms. After we started using Angular Material in our application and to fix issues with forms, this library helped us to replace the previous one. Our application has grown into big and we stuck at version 6 as of now and using 2.1.9. As said by @MichielMag, we also customized the Calendar CSS to match our styling. It's ok for us to not to have material dropdown everywhere. So, my choice would actually be number 2, to revive v2.
Hi @fetrarij ,
I am using V2.2.10 ngx-daterangepicker-material as my project is based on AG6. And this calendar is really helped me to fulfill my purpose to add range picker in my project. As others mentioned I also worked on CSS customization but it is fine for me. So i would like to go with second option that please upgrade V2 version as in this version some latest features are not present.
Thankyou :)
Hi @fetrarij,
I would agree with the others. With the official Material component I think it makes more sense to go with v2 revival. Official component is missing some of the features from this library so I think it would still have a lot of value.
yes, upgrade and support to ngx daterangepicker material is really required. I am using this in my project and it helped a lot for me. it's really amazing datepicker.
On Fri 10 Jul, 2020, 3:54 PM Marko Vukosavljević, [email protected] wrote:
Hi @fetrarij https://github.com/fetrarij,
I would agree with the others. With the official Material component I think it makes more sense to go with v2 revival. Official component is missing some of the features from this library so I think it would still have a lot of value.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fetrarij/ngx-daterangepicker-material/issues/308#issuecomment-656603317, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKTPOL2HY2YJ3RYF4M4YZ4DR23T4VANCNFSM4OUSSFMA .
Hello @fetrarij
I would also go with option 2. Being independent from material would also provide the ability for more users to use this library without necessarily being forced to use material, let alone that currently it has more features than the corresponding material implementation and better UI and layout in my opinion.
@fetrarij Option 2 anytime as its good to keep it customisable. It's easy to implement and use.
i would really like to continue using ngx-daterangepicker and i would like it more if it is customisable. Hence i am going with option 2.
Please don't kill it, we just adopted it in a production app :) I really needed those weeknumbers and for some reason the Angular Material guys don't want to include it as it's not part of the material spec.
I would like to go with option 2 It has better implementation, functionality and can use it in projects without being forced to use angular/material. Being able to customize it also a plus.
Option 2 would be my choice. Maybe replacing momentjs with luxon, dayjs or date-fns :)
Hi, just to let you all know that v5 is out and momentjs is replaced with dayjs
That's great 😀.
I will update soon.
Regards, Rituja
On Sat, 12 Jun, 2021, 12:16 am Fetrarijaona R., @.***> wrote:
Hi, just to let you all know that v5 is out and momentjs is replaced with dayjs
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fetrarij/ngx-daterangepicker-material/issues/308#issuecomment-859773098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZWJTAUNWPHURUB2UJ553LTSJKYLANCNFSM4OUSSFMA .