Is this repo being maintained?

[chickendiver]

Looking to see if this repo is maintained anymore, or if a transition plan is in place.

Looks like there are plenty of recent PRs, but no activity since November from the repo's primary owner.

If this is being maintained, or if there is a fork that is being maintained regularly to keep this alive, please say so in the thread below!

[jimmywim]

Nope, completely dead from what I can tell.

And from 488 forks, it'll be hell to tell which one is the most active.

[bflamand]

Anyone has an active fork with support for react 18 ?

• fix for the "componentWillReceiveProps" issue?
• and ideally typesccript fixes for react18 also? (i know they are maintained elsewhere...)

[Ilaiwi]

looking for maintainers

[gerich-home]

Anyone has an active fork with support for react 18 ?

• fix for the "componentWillReceiveProps" issue?
• and ideally typesccript fixes for react18 also? (i know they are maintained elsewhere...)

Looks like some folks try to upgrade to the latest React in their forks.
See this commit cm-xlabs@8cebc8c
in https://github.com/cm-xlabs/react-calendar-timeline

@aholtkamp could you please tell what is the current status of your fork, what is remaining to upgrade to React 18?

[aytech]

I've upgraded my project to react 18, and everything works with the timeline. I had to do some smaller modifications, like async groups breaking the dragging, other than that it seems to be compatible

[aholtkamp]

Anyone has an active fork with support for react 18 ?

• fix for the "componentWillReceiveProps" issue?
• and ideally typesccript fixes for react18 also? (i know they are maintained elsewhere...)

Looks like some folks try to upgrade to the latest React in their forks. See this commit cm-xlabs@8cebc8c in https://github.com/cm-xlabs/react-calendar-timeline

@aholtkamp could you please tell what is the current status of your fork, what is remaining to upgrade to React 18?

Initially we just wanted to get rid of the warning about "componentWillReceiveProps". While fixing this was easy we wanted to make sure that the tests also run in React 18 to get a rough impression if everything works as expected. This actually was the major part if the upgrade as it required third party upgrades and getting rid if enzyme.

So current status:

• no more warning
• tests run on React 18

Probably upcoming:

• additional third party upgrade to fix security vulnerabilities
• some performance tweaks

[Ilaiwi]

@aholtkamp are you are interested in maintaining the library?

[aholtkamp]

@aholtkamp are you are interested in maintaining the library?

Too early to say, we just started with the component in our project. However, if any of these changes has a chance to be included in a release coming from this repository I'd like to contribute by creating a pull request.

[MertHaddad]

I am interested in contributing if there's someone still working on it

[florianbepunkt]

@MertHaddad
I'm evaluating to pick this up and started working on a fork, based on other forks and PRs. But it is in a very initial phase.

Some technical goals:

• react 18 compat [x]
• replacement of react legacy apis / strict mode compat (20%) []
• removal of moment.js (90% done) []
• refactor code to use typescript []

@Ilaiwi How stable are the tests for this project? What is your level of confidence in them?

I can't promise anything, but we are using this library in a project we would like to continue. I will report back, once I jave something more to show, but it might be a few weeks to months. If anyone has tackled typescript refactoring for this project, please let me know.

[Ilaiwi]

@florianbepunkt the unit tests are solid but the coverage is not great. I would recommend checking this fork.

[florianbepunkt]

@Ilaiwi Oh, this is perfect. Thank you.

[Ilaiwi]

@florianbepunkt please let me know about the progress you do. Since I don't really use this library anymore it is hard to evaluate forks.

[MertHaddad]

@florianbepunkt
We're using it in a project as well, so let me know if you need a help.

[florianbepunkt]

Quick update. Time is limited, but I used the fork @Ilaiwi mentioned above as a base. Here is what works so far:

• typescript [x]
• react 18 compat [x]
• removal of moment.js [x]
• replacement of react legacy apis / strict mode compat (20%) []
• move to ESM only module []
• modernize test structure (react testing library, unified test structure) (25%) []
• refactor / code cleanup (dead / unused code, out of date documentation) []

The problem is that I need to reimplement a lot of the tests.

Also, while moment as a dependency is gone, currently there is a lot of moment.js legacy glue code... e. g. format tokens that are used by moment.js but are non-standard. Ideally, I would like to get rid of this and move to date-fns, as it uses native date objects / timestamps.

@Ilaiwi What are your future plans? I likely won't have the bandwidth to add features to this repo. We use a certain feature set for our project, so not sure what to do with my work, once it's done. Let me know, if you want a pr, but it would be quite heavy...