Document removal of deprecated DateTime dialog fields (MM-68396)

[sbishel]

Summary

• Removes the deprecated min_date/max_date (top-level on date elements), min_date/max_date/time_interval (top-level on datetime elements), and datetime_config.allow_manual_time_entry rows from the Interactive Dialog docs, since these fields have been removed server-side in server version 12.0.
• Adds a "DateTime field breaking change (server version 12.0)" callout in the datetime_config object section explaining that these values must now be sent under datetime_config (using manual_time_entry instead of allow_manual_time_entry), and that un-migrated payloads will have them silently ignored.

Related

• mattermost/mattermost#MM-68396 — server/webapp removal of the same deprecated fields

Ticket Link

Fixes: https://mattermost.atlassian.net/browse/MM-68396

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 2548a30

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates interactive dialog documentation to remove deprecated top-level date and datetime fields, direct integrations to nested datetime_config, and document related server version 12.0 breaking changes.

Changes

Interactive dialog configuration

Layer / File(s)	Summary
Document nested datetime configuration site/content/integrate/plugins/interactive-dialogs/_index.md	Removes deprecated top-level fields from the date and datetime tables and documents their removal or replacement under datetime_config for server version 12.0.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the doc update removing deprecated DateTime dialog fields.
Description check	✅ Passed	The description is directly related and accurately describes the documentation changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch MM-68396-remove-deprecated-fields

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@site/content/integrate/plugins/interactive-dialogs/_index.md`:
- Around line 581-583: Update the breaking-change note so `time_interval` is
described as a removed top-level field only for `datetime` elements, while
keeping `min_date` and `max_date` scoped to both `date` and `datetime` elements.
Preserve the existing guidance to send `time_interval` under `datetime_config`
and rename `allow_manual_time_entry` to `manual_time_entry`.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fde28efa-de62-4645-b157-18d4b053ff1d

📥 Commits

Reviewing files that changed from the base of the PR and between 9755670 and 2548a30.

📒 Files selected for processing (1)

• site/content/integrate/plugins/interactive-dialogs/_index.md

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 41d4de2

[hanzei]

Thanks!

[hanzei]

Suggested change

	The top-level `min_date`, `max_date`, and `time_interval` fields on `date`/`datetime` elements, and the `datetime_config.allow_manual_time_entry` field, have been removed. Integrations must send these values under `datetime_config` (using `manual_time_entry` instead of `allow_manual_time_entry`) or they will be silently ignored.
	The top-level `min_date`, `max_date`, and `time_interval` fields on `date`/`datetime` elements, and the `datetime_config.allow_manual_time_entry` field, have been removed with Mattermost v12. Integrations must send these values under `datetime_config` (using `manual_time_entry` instead of `allow_manual_time_entry`) or they will be silently ignored.