Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ui): UI fixes #1945

Merged
merged 5 commits into from
Feb 23, 2024
Merged

fix(ui): UI fixes #1945

merged 5 commits into from
Feb 23, 2024

Conversation

hdinia
Copy link
Member

@hdinia hdinia commented Feb 23, 2024

No description provided.

@hdinia hdinia requested a review from skamril February 23, 2024 12:46
@hdinia hdinia self-assigned this Feb 23, 2024
@makdeuneuv makdeuneuv linked an issue Feb 23, 2024 that may be closed by this pull request
@@ -148,15 +149,27 @@ function ResultDetails() {
},
);

// !NOTE: Workaround to display the date in the correct format, to be replaced by a proper solution.
const dateTimeFromIndex = useMemo(() => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add it in usePromise instead of creating a useMemo.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to not mix it with the matrix promise and keep clear separation of concerns. For the useMemo, the index array in matrixRes.data is large, making date formatting expensive. If we trigger a filter for example it will be re-calculated.
don't you think we should keep it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it's workaround before the backend fix it, I think it's correct to place it in the usePromise.
As you want.

@@ -6,7 +6,7 @@ export const Root = styled(Box)(({ theme }) => ({
display: "flex",
flexDirection: "column",
alignItems: "center",
overflow: "auto",
overflow: "hidden",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure you don't break anything? Test with big matrix.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Handsontable docs recommands the parent container overflow is set to "hidden", normally it doesn't break anything i've tested

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doc recommands auto or hidden. If you're sure ok.

@skamril skamril self-requested a review February 23, 2024 15:38
skamril
skamril previously approved these changes Feb 23, 2024
@skamril skamril merged commit 5dd2711 into hotfix/v2.16.5 Feb 23, 2024
6 checks passed
@skamril skamril deleted the hotfix/ui-fixes branch February 23, 2024 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add timestamp in results
2 participants