-
Notifications
You must be signed in to change notification settings - Fork 15
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: PageLoading component message and translation #369
base: main
Are you sure you want to change the base?
fix: PageLoading component message and translation #369
Conversation
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should handle I18n the same way in all components. This solution is different from other components. For sake of uniformity I suggest to simply expose the noRowsMessage
prop
@@ -53,6 +53,7 @@ export interface PageLoadingTableProps<Row, Args> | |||
allItems?: Row[] | |||
callbackToPage?: (data: PaginResult<Row>) => void | |||
allItemsLoadedHint?: string | |||
mappedTableSearchTranslation?: Record<string, string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Usmanfee In the existing components we simply pass the message in the current language, so the suggested solution works differently. See my comment in the ticket: #368 (comment)
Description
Added translation mapped object to PageLoading component to display messages in EN and DE.
Changelog entry:
Why
PageLoading component always displaying hardcoded message in case of absence of Table data and table data against user typed search keywords.
Issue
#368
Checklist