jedcunningham opened a new pull request, #74818:
URL: https://github.com/apache/airflow/pull/74818

   Fixes to the Dag version comparison (Versions tab):
   
   **Empty "Max changes" field no longer shows an error border.** The number 
input treats an empty value as NaN, so zag's `isOutOfRange` marked the field's 
normal, unset state invalid. `Versions.tsx` now passes `invalid` explicitly: 
only a non-empty value that is not an integer in 1..5000 is invalid.
   
   **Clearer messaging when the limit cuts the comparison short.**
   - The summary says "At least N changes" instead of "N changes", since the 
count is a lower bound once truncated.
   - The warning now reads "Showing only the first N changes" / "There are more 
changes than the Max changes limit allows. Raise the limit to see the rest." 
(or names the default limit when the field is empty), replacing "Changes at 
paths not shown were dropped to stay within the limit, so the count is a lower 
bound."
   - The table's own "N Records" heading is hidden. It repeated the change 
count in the summary just above it, and could disagree with it, because a 
redacted record stands for every change sharing its path.
   - The old `versions.truncated.*` strings are removed from the seven 
translated locales so they fall back to English rather than show the old 
meaning; translators can add the new keys.
   
   
   Comparison of two versions with more changes than the default limit (500), 
Max changes left empty.
   
   Before (main):
   
   
   
   <img width="1031" height="440" alt="Screenshot 2026-10-15 at 4 22 13 PM" 
src="https://github.com/user-attachments/assets/99a5a499-8999-4244-a0c3-278ef5981751";
 />
   
   
   After:
   
   <img width="1035" height="470" alt="Screenshot 2026-10-15 at 4 22 33 PM" 
src="https://github.com/user-attachments/assets/96744eab-30e1-4c9d-8e8a-f998e2b83b8f";
 />
   


-- 
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]

Reply via email to