Skip to content

fix(chat): apply maximum permitted message deletion scope - #32

Merged
Neup123 merged 1 commit into
mainfrom
fix/delete-message-auto-scope
Sep 22, 2026
Merged

Neup123 merged 1 commit into
mainfrom
fix/delete-message-auto-scope

Conversation

@Neup123

@Neup123 Neup123 commented Sep 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • keep one backward-compatible Delete Message endpoint
  • automatically select the strongest permitted scope:
    • connected account message: delete for everyone
    • another participant's group message while admin: delete for everyone
    • another participant's direct message or group message without admin permission: delete for this account
  • fall back to delete for this account when a revoke cannot be confirmed
  • report the applied scope and confirmation state explicitly
  • expose guided Swagger form fields while retaining JSON input
  • document request fields, webhook mappings, response semantics, and fallback reasons
  • add focused deletion and runtime OpenAPI validation

Validation

  • npm run test:delete-message
  • npm run lint:check
  • npm run audit:runtime-openapi
  • npm run audit:chat-docs
  • npx tsc --noEmit
  • npm run build
  • git diff --check

Refs #22
Fixes #28

@Neup123
Neup123 merged commit f6a47c1 into main Sep 22, 2026
4 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.

Swagger Try it out: render request-body properties as form fields

1 participant