RoyLee1224 opened a new pull request, #51558:
URL: https://github.com/apache/airflow/pull/51558
### Related Issues
#50861
### Translated Pages
- **Assets**
- **Browse**
- Audit Log
- XComs
- **Admin:**
- Variables
- Pools
- Providers
- Plugins
- Connections
- Config
### Other Changes made
- Slightly changed delete layout to be more consistent with bulk delete.
- before
- after
### Discussion Point: Dynamic Connection Fields
While most static text on the Connections page has been translated, I've
encountered a challenge with the dynamically generated fields.
- **The Challenge**: The **"Standard Fields"** and **"Extra Fields"**
sections are rendered based on the selected "Connection Type". The labels for
these fields (e.g., `Host`, `Port`, `Login`, or provider-specific fields like
`ADLS Gen2 Account Name` ) appear to be defined in English on the backend.
- **My Question**:
- Should these labels be added to the frontend JSON translation files?
- Or is there a backend mechanism for their translation that should be
used instead
- Or, should we leave these in English
### Screen Shots for Dynamic Connection Fields
I would greatly appreciate feedback and guidance on the appropriate way to
proceed with these dynamic fields.
<!--
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]
