Reaching out to developers/maintainers

[rjray]

I tried emailing @Ilaiwi (as we've corresponded before) but not heard back, so I'm reaching out here. I would be happy to hear from either @Remco4EF or @remcoblumink.

My company is using this package in an internal application. We are trying to manage with the 0.30.0-beta.3 release, but there are a number of rough areas. I am currently trying to get permission to spend some (probably small) chunk of my work-time on contributing to this project, addressing known bugs, adding some things that we specifically need (better documentation, more control over the CSS for light/dark modes, and others). Even if they turn down my request, I will somehow clear out a few hours of personal time each week to do whatever I can.

I do need to know the current status of the outstanding pull requests, at least those that are dated after the most-recent release was created, and outstanding issues. I am guessing that at least some part of what was filed prior to the TypeScript rewrite is no longer relevant, so I just want to make sure that I don't try to fix something that is not currently an issue.

Once I'm in contact with maintainers, I'll file a number of bug and enhancement issues so that I can use them for tracking purposes. Some of what we need includes:

• Ability to override or completely suppress the onClick handlers for headers. We wish to limit the zoom-in ability, and the hack I currently have in place is very brittle.
• Moving hard-coded CSS into defined, documented classes. For example, the TodayMarker element hard-codes its CSS and as such it disappears in dark mode.
• Fixing a bug in DateHeader when unit is passed as primaryHeader.
• Ability to pass a ref in to the creation of the calendar itself, so that we can attach observers to act when scrolling is close to the bottom of the current content (we could conceivably try to create over 28K rows in some edge cases, so we need to only render a visible window rather than everything).

There may be more over time, these four are the most-pressing that we currently have.

Randy (@rjray)

[Ilaiwi]

Hi @rjray , sorry that I have missed your email. I will reply to it hoping we can figure something out here.

[lnagel]

Hello @Ilaiwi and others! From our side we will dedicate some more resources toward this library now as well From our team @developer-ocansey is available to assist with maintenance. I'll drop you an email on the subject as well in a moment.