List and join efforts with menu_item_fields

Could this module please be listed as alternative to the module page?
https://www.drupal.org/project/menu_item_fields →

Vice versa menu_item_fields should add this module? @rodrigoaguilera

Added this module as alternative module. Although it was already listed as inspiration I added a link to this issue so we can discuss here.

Hi @rodrigoaguilera and @Anybody, I was just made a maintainer of this module with the goal to get a D10 release.

This module is under minimum maintenance so I am happy about the efforts to go on https://www.drupal.org/project/menu_item_fields → fully as the code seems really robust and it offer more features than this module.

I will mention this module as a suggested alternative in the project page.

Great that this can move forward.

It has been a while since I don't check the situation of both modules.
Surprisingly menu_item_fields has 1437 sites using the module while menu_link_content_fields has 66.

@fjgarlin
It is not clear to me the next actions you plan as maintainer of this project. Are you still going to release a D10 version?
From having a look at the code I think you can install menu_item_fields and uninstall menu_link_content_fields without losing any data.
No breaking changes should happen either since the new features depend on using the new block provided to display menus.

With so few sites using it I feel reluctant to write a detailed migration path.

I’ve already created a D10 release and also added a link to the other module in the project page.

Happy to do more things if needed but i wasn’t planning as the module was already marked as minimally maintained.

Well as of #6 it might be a good idea to perhaps even deprecate this module for the other one, so that for further Drupal major releases no further coding is required?

Maintainers should decide :) But why invest the time and work twice... better help with the mature module.

Marked as deprecated, obsolete, and also highlighted the alternative modules with a big warning div.
Hopefully it is clearer now: https://www.drupal.org/project/menu_link_content_fields →

Totally agree with going with the more mature module.

With so few sites using it I feel reluctant to write a detailed migration path.

Agree.

Automatically closed - issue fixed for 2 weeks with no activity.