Will version 1.9.x be maintained forever?

[jiaozhiye]

Can all Props and Event names from 1.9.x be retained? Because my layout data is shared with react-grid-layout, I hope that both parties can share the same data. I also hope that the 1.9.x version will be maintained. Thank you.

[xmatthias]

I personally doubt that an old version will be "maintained forever". From a maintainer's standpoint, that's not feasible unless you've got a very big team (you have to maintain 2 parallel versions of the same library).

The change in the interface from i to id is a silently breaking change (release log didn't really mention any breaking changes - just "rewrite new props" - and the PR doesn't have any description ... ) - so i'm not even sure it's intentional that it broke people's apps.

It seems like an unnecessary change, really - with the side-effect that everyone's stored local data (for the layout) now has to be either migrated or reset.

---

Now I don't mind changes per se ... but they should be highlighted as "breaking" to avoid blindsiding people unnecessarily.

Unfortunately, the way it currently looks - this library isn't really stable since it changed maintainers ... not sure what the actual plans for this project are (all i know is that this is the 3rd problematic update in recent months, with 2 others breaking the app by missing exports or similar #23, #35).

If the changes are necessary - no problem - but they should be

• highlighted as breaking changes in the changelog
• better communicated (like - the PR should have a description - for future observers to understand reasons for changes)

[jiaozhiye]

I personally doubt that an old version will be "maintained forever". From a maintainer's standpoint, that's not feasible unless you've got a very big team (you have to maintain 2 parallel versions of the same library).

The change in the interface from i to id is a silently breaking change (release log didn't really mention any breaking changes - just "rewrite new props" - and the PR doesn't have any description ... ) - so i'm not even sure it's intentional that it broke people's apps.

It seems like an unnecessary change, really - with the side-effect that everyone's stored local data (for the layout) now has to be either migrated or reset.

Now I don't mind changes per se ... but they should be highlighted as "breaking" to avoid blindsiding people unnecessarily.

Unfortunately, the way it currently looks - this library isn't really stable since it changed maintainers ... not sure what the actual plans for this project are (all i know is that this is the 3rd problematic update in recent months, with 2 others breaking the app by missing exports or similar #23, #35).

If the changes are necessary - no problem - but they should be

• highlighted as breaking changes in the changelog
• better communicated (like - the PR should have a description - for future observers to understand reasons for changes)

I can't understand why the parameter model needs to be changed, such as the layout model and event names. Although react-grid-layout is not a standard, but it has a certain user base. If both sides can maintain the same parameter type, it will definitely bring a better development experience, so I can’t understand why such a meaningless change should be made in the new version!

[xmatthias]

Based on having a new version - but no response here - it seems like maintainers don't really care.

it's rather unfortunate that there's no alternatives to this library with vue3 at this point.