Conversation
e30243a to
6052c97
Compare
|
Nice to move to MUI components, it's better for the coherence. But I think we should improve the current display too. Maybe not related to this PR, but currently the width is really small + misplaced (not located under the button). |
Agree, the filter somehow does not align with the column, so there is no context of what I'm filtering. |
For the misalignment I found and opened a an issue yesterday. This is not coming from this change and has been there from the beginning. Look at this I am not really sure, what would be the best way to keep them aligned in case the table scrolls. I don't want to spend too much time over UI improvements in this task. So, could we think about the misalignment issue later? |
|
Yes it was suggested already by @Gladorme. We agree there is an issue, but we know is not part of these changes, it existed before. |
561a827 to
3c55b41
Compare
Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com> Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com>
3c55b41 to
9aed6a8
Compare
I improved the size, so it fits the filter header. It has been demonstrated in the screenshots attached to description. There is still an old issue with the hidden dropdown when it gets lengthy. This should be addressed with a separate PR.
It would be great if you could review now. |
| const values = [...new Set(allValues)].filter((v) => v !== null).sort(); | ||
|
|
||
| if (!values.length) { | ||
| return ( |
There was a problem hiding this comment.
We should render this dropdown inside a Portal, this will avoid the clipping. The table plugin uses it's own implementation which also has this issue. But fixing it here will make it consistent for both logs and table plugins.
| position: 'absolute', | ||
| top: '100%', | ||
| left: 0, | ||
| zIndex: 9999, |
There was a problem hiding this comment.
| zIndex: 9999, | |
| zIndex: 1000, |
This will make it above other elements but below the sticky header, when using the Portal
There was a problem hiding this comment.
const [filterAnchorEl, setFilterAnchorEl] = useState<{ [key: string]: HTMLElement | undefined }>({});
I was checking your comment when I realized there is no usage of this sate in the code. This is coming from the original code. Even in the original code this line has no usage! Am I mistaken, is there any usage that I am missing?! filterAnchorEl is never used for any kind of calculations. I think, the dropdown used to be a popover. Later changed, and this line became obsolete. I am not sure though.
Update
OK, a bit of this a bit of that! I guess the original idea was to use an anchor and MUI popover.
Looks nice!
⚠️ IMPORTANRT: Popover is a kind of modal. It covers the entire page, so elements beneath the Popover could not be reached as long as the Popover is not closed.
Signed-off-by: Mahmoud Shahrokni <seyedmahmoud.shahrokni@amadeus.com>
|
Yes this just uncovered a big issue with our current table, we probably should migrate and use a DataGrid instead which already has all these features. |






Description 🖊️
This PR is moving the filtering section of the Table Panel (from plugin side) into the Table component (shared repo)
As previously discussed, the table and the filter should be logically integrated. Currently, they are treated as separate entities. An investigation of the Table plugin reveals that the filter section was added as a later addition on top of the existing Table component.
The PR
Subsequent Changes 🏃🏼
After the PR is merged, and the shared version is updated in the plugin
Checklist
[<catalog_entry>] <commit message>naming convention using one of thefollowing
catalog_entryvalues:FEATURE,ENHANCEMENT,BUGFIX,BREAKINGCHANGE,DOC,IGNORE.UI Changes
See e2e docs for more details. Common issues include: