RoyLee1224 opened a new pull request, #51209: URL: https://github.com/apache/airflow/pull/51209
## Why introduce `noItemsFound` as an improved default fallback For pages that currently lack a customized noRowsMessage, DataTable will now display a fully translated message. For example, instead of an erroneous "No 任務實例 found" (a mix of English and Chinese), the UI will correctly render a message like "找不到任務實例". ## Why is the `noRowsMessage` prop still crucial Relying solely on this generic template with modelName interpolation is insufficient due to complex grammatical rules in some languages. For example: - Korean: Grammatical object markers (을/를) change based on whether the modelName ends in a vowel or a consonant. - German (and other languages with complex plurals/noun forms): The plural of modelName in German might be entirely different, we cannot simply add 's' after modelName in "common:noItemsFound", like English. Therefore, the long-term goal is to increasingly utilize the `noRowsMessage` prop to provide fully tailored messages. ## Additional information For more information on such practices, please refer to: [i18n Best Practices for Front-End Developers](https://shopify.engineering/internationalization-i18n-best-practices-front-end-developers) <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> <!-- Please keep an empty line above the dashes. --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
