kir-rin commented on code in PR #66266:
URL: https://github.com/apache/airflow/pull/66266#discussion_r3177785360
##########
airflow-core/src/airflow/ui/public/i18n/locales/ko/dag.json:
##########
@@ -40,6 +40,12 @@
"parseDuration": "파싱 기간:",
"parsedAt": "파싱 시간:"
},
+ "deadlineStatus": {
+ "stillRunning": "실행 중",
+ "upcoming": "예정",
Review Comment:
For `deadlineStatus.upcoming`, I chose **"예정"** over **"데드라인 전"**:
| Option | Pros | Cons |
|--------|------|------|
| 예정 | Concise, no redundancy | Ambiguous - could be confused with scheduled
runs |
| 데드라인 전 | Explicit, clear context | Redundant under "Deadline" header |
Since the badge already appears under the "Deadline" section header, "데드라인
전" felt repetitive. However, I'm still unsure if "예정" is clear enough in
Airflow context where "scheduled" is a core concept. Open to alternative
suggestions that balance clarity and conciseness.
--
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]
