Skip to content

refactor(imap): revert getSource -> getRawMessage rename - #13610

Merged
ChristophWurst merged 1 commit into
nextcloud:feat/jmap-2from
ChristophWurst:chore/jmap-2-revert-getsource-rename
Sep 2, 2026
Merged

ChristophWurst merged 1 commit into
nextcloud:feat/jmap-2from
ChristophWurst:chore/jmap-2-revert-getsource-rename

Conversation

@ChristophWurst

@ChristophWurst ChristophWurst commented Sep 1, 2026

Copy link
Copy Markdown
Member

Slimming down #12800.

The rename touched the OCS route id (mail.messages.getSource -> ...getRawMessage) with no behavior change and no stated reason, unrelated to the JMAP protocol work. Restore the original name to drop this from the JMAP diff; the OCS route id and controller/service method name are back to what main already has.

Assisted-by: ClaudeCode:claude-opus-4-8

馃 AI (if applicable)

  • The content of this PR was partly or fully generated using AI

The rename touched the OCS route id (mail.messages.getSource ->
...getRawMessage) with no behavior change and no stated reason,
unrelated to the JMAP protocol work. Restore the original name to
drop this from the JMAP diff; the OCS route id and controller/service
method name are back to what main already has.

Assisted-by: ClaudeCode:claude-opus-4-8
Signed-off-by: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
@ChristophWurst
ChristophWurst force-pushed the chore/jmap-2-revert-getsource-rename branch from b6af25d to e89fad8 Compare September 2, 2026 06:31
@ChristophWurst
ChristophWurst merged commit e9d0450 into nextcloud:feat/jmap-2 Sep 2, 2026
33 of 45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant