[Bug/Discussion][SF][2.5.0][Table][Function][Expected reply Time: ASAP] Fix the version 1 table or have different tags?

[wilson-xu-sap]

Describe the bug

Since table in version 1 is different from that in version 2, some issues in version 1 no longer exist in version 2. However, for those complicated tables, it is hard to migrate to version 2. Then questions come,

1. Could you make fixes available in v1?
2. When will you deprecate v2 table?
3. Could we make table tags different to make two versions co-exist?

Isolated Example

No response

Reproduction steps

No response

Expected Behaviour

No response

Screenshots or Videos

No response

UI5 Web Components for React Version

2.5.0

UI5 Web Components Version

2.5.1

Browser

Edge

Operating System

No response

Additional Context

No response

Relevant log output

Organization

SF

Declaration

• I’m not disclosing any internal or sensitive information.

[Lukas742]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[unazko]

Hello @SAP/ui5-webcomponents-topic-core,

Could you please review those questions.

Best regards,
Boyan

[pskelin]

Hi @wilson-xu-sap ,
here is a code snippet with which I was able to change the tag under which one of the tables is registered:

// v2 table is imported and registers the `ui5-table` tag
import "@ui5/webcomponents/dist/Table.js";
// v1 import runs registration which will fail silently because tag is taken
import TableCompat from "@ui5/webcomponents-compat/dist/Table.js";

// change tag
TableCompat._metadata.metadata.tag = "ui5-table-v1"

// run define again to register with new tag
TableCompat.define();

Result in DOM:

you can change the order if you want v2 table to have the new name.

to your questions:

1. Could you make fixes available in v1?

usually yes, fixes can be made in v1. some of them however are quite complicated and require a full restructuring, hence why v2 table was created - to address hard to fix issues.

2. When will you deprecate v2 table?

hopefully not in a very long time. v1 table was more of a quick implementation until the complex full implementation can come. v2 is considered feature rich and future proof. keep in mind that it is currently experimental and some APIs can change, also according to your feedback. perhaps @simlin can comment on this better.

3. Could we make table tags different to make two versions co-exist?

Yes, see the snippet above. Let me know if you have any issues with making it run.

[simlin]

The plan is to remove the experimental flag of the V2 table soon, depending on incoming changes which might cause incompatibilities. These should be handled first for sure.
The v2 table should be the successor of the first implementation. There is for sure currently no plan for a deprecation