This meta issue tracks the work needed for the next major version of this module.

The goal of the new major is to address standing issue from both UX and functionality side.
A non-exhaustive list of points to address:

  • remove complex code like single "child element" default value handling;
  • UX improvements around fixed cardinality elements: rely on the "Add more" button instead of pre-rendering all items;
  • Add a remove button per row;
  • Better detection of empty rows;
  • Simpler handling of default values: possibly allow to process values "to" and "from" form (like ConfigTarget does).
CommentFileSizeAuthor
#3 mvfe-2x-integration.patch103.05 KBdarvanen

Comments

sardara created an issue. See original summary.

darvanen’s picture

darvanen
he/him
Primary language English
Location Sydney, Australia
commented

My current plan of attack:

darvanen’s picture

darvanen
he/him
Primary language English
Location Sydney, Australia
commented
StatusFileSize
new mvfe-2x-integration.patch103.05 KB

I've gone way ahead and made a patch that combines fixes for all the issues in the plan in #2. Attaching it here in case anyone wants it, or for maintainers to see the finished product.

I've posted a series of patches that shouldn't conflict, there's about 3 waves of those in this combined patch.

sardara’s picture

sardara commented

Thanks @darvanen for the patches. I want to state though that, for users of these patches or this patch in #3, especially for functionalities such as #default_value_callback, that I have not validated the approach yet on that code, so it might be completely changed before the issues lands merged.