mirror of
https://github.com/mattermost/mattermost.git
synced 2026-11-05 13:47:13 -06:00
Ben SchumacherandClaude Opus 5.5
47b81751a4
* [MM-71403] Add a custom from/to time range to the Server Logs viewer Adds a "Custom range…" option to the Duration menu that opens a dialog with From and To date and time pickers in the admin's timezone. Both bounds are sent to the logs query, the end covering its whole minute, and the client-side time backstop now applies the upper bound too. Live tail is turned off and unavailable while a custom range is set. Picking today in DateTimeInput no longer resets the chosen time to now when past dates are allowed. * [MM-71403] Trim the custom range docs note * [MM-71403] Block invalid range times and pick the year in the user's timezone - Keep Apply disabled while a typed time is invalid or cleared. DateTimeInput reports manual time errors through a new optional onTimeInputError callback. A cleared field that still holds a time now shows the error border, also in app forms. - Decide whether the range label shows the year in the user's timezone. - Pin the clock in the custom range tests. - Use Compass tokens in the custom range modal styles. * [MM-71403] Fix the three defects found by automated QA - Custom range dialog: the cap on both pickers now follows the current minute while the dialog stays open, instead of staying at the minute it was opened. Typing the minute it now is no longer snaps back. - Duration field: a range shown with years gets a wider field, so a cross-year label like 'Dec 31, 2025, 11:00 PM – Jan 1, 2026, 1:00 AM' is no longer cut off. - DateTimeInput: picking the day that is already selected now restores a cleared manual time and clears its error, like picking another day. Before, it only reset when the stored time changed, which a same-day pick doesn't do in app forms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FpCfx5tK9UfjDiH2sPNKG1 * [MM-71403] Block Apply when an invalid time is clicked away from The manual time field passed its error up from an effect. An update made in an effect waits for a scheduler task, so a click on Apply that blurred an unparseable time could land first and apply the previous range. The error is now reported from the handler that finds it, like a valid time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FpCfx5tK9UfjDiH2sPNKG1 * [MM-71403] Check the exact bounds a custom range sends in the e2e test The custom range test only checked that both dates were well formed, so a later end would still pass. It now checks the end is the last millisecond of the minute the dialog opened in, and the start an hour before it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FpCfx5tK9UfjDiH2sPNKG1 --------- Co-authored-by: Claude <noreply@anthropic.com>