feat: ellipsis on table cell

[mizek1]

Sometimes we have a large information to show on a column, that makes a cell too large on both aspects, width and height:

We need to be able to, when we set a width on a column, we can also set if that column could be partially hidden using ellipsis properties. We also need that, when we decide to use ellipsis on a column, the table automatically shows a tooltip with the complete information. Something like this:

[luccskywalker]

Qual o sentido de ter uma tabela que esconde o que eu estou mostrando nela?
Esse comportamento me parece mais um acordion do que uma tabela.

[mizek1]

Qual o sentido de ter uma tabela que esconde o que eu estou mostrando nela?
Esse comportamento me parece mais um acordion do que uma tabela.

The default behavior is to show all information, this feat will only allow the possibility to hide part of the information that can be hidden. Every project has it's own specifications.

[luccskywalker]

I've forgotten only English in here.
So, you will define the criteria to hide the content, how do you will control it.
If these steps are not well specified it only will bring a behavior unnecessary to the component.
The master proposition of a table is to show information, not to be pretty. Can be both obviously but if these two principles collides, i think that display the info should have more weight on the criteria selection.

[mizek1]

"The master proposition of a table is to show information". Yes, it is, that is why we need the ellipsis on huge information, in the first place. On a page, we need that our user see more data on the available space and find the item they want. How do you feel, as a user, when you enter on a page and see this?

I understand that a table doesn't need to be pretty, but we also need to garantee that a user find the information in the fast way possible, because that's why we use tables.

[mizek1]

What do you guys think of these solution? Any other idea to solve this problem?
@iurynogueira @andersonnagelo @Jeter-Megaron @qrayannes (I can't find Edney's user)

[luccskywalker]

If the user is not finding the information that him needs, the column is not representing their necessity.

[edneyql]

@mizek1 @luccskywalker Sometimes the solution may not be a table, the solution could be related to another component... As I don't understand the context of the demand itself, I can't say so much if in this case it would be a table or not , but regarding the density of information, it also interferes with the user's cognitive process and loses the meaning of the component that serves to systematize the information, which must be presented in a clear and precise way, to facilitate the reading and understanding of the data. If I have a table that brings me such a high density of data and I can't deal logically with it, I have to rethink whether I'm using the right component for the solution.

[AlyssonMascarenhas]

@edneyql what if the table is just a way to extract through actions?

[AlyssonMascarenhas]

I believe we can create a discussion at github.com/Brisanet/ion/discussions instead of discussing it here in the issue.

[Jeter-Megaron]

The solution has already been aligned with the SIGA team, we are going to suppress the column information in the table, the user will be able to see all the data related to the selected profile with 1 additional click on the detailing column of the desired line.

[iurynogueira]

Guys, can follow with this implementation because can have other cases to use this abbreviation too. We need give other options to the dev and this improve will be more one.