Skip to content

Conversation

@joshishiv4
Copy link
Owner

We want to use only ISO 8601 formats with the <time:> syntax, so we remove the previous comment recommending the usage of <time:dep_time>, and instead add a (commented-out) function that converts the datetime to the right format.

How did you test this PR?
I did not.

Self-review checklist
  • Self-reviewed the changes for clarity and maintainability
    (variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

  • Explains differences from previous plans (e.g., issue description).
  • Highlights technical choices and bugs encountered.
  • Calls out remaining decisions and concerns.
  • Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

  • Each commit is a coherent idea.
  • Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

  • Visual appearance of the changes.
  • Responsiveness and internationalization.
  • Strings and tooltips.
  • End-to-end functionality of buttons, interactions and flows.
  • Corner cases, error conditions, and easily imagined bugs.

Recreated from zulip/python-zulip-api#889

⚠ This PR was MERGED upstream.
Merged at: 2025-12-05T02:10:26Z

Niloth-p and others added 4 commits December 5, 2025 06:02
While the message template customization function had `dep_time` and
`dep_id` parameters, the `deployment` dict was not populated with those
fields previously.
Co-authored-by: Anders Kaseorg <anders@zulip.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants