Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2217
Closed
Open
Issue created Oct 05, 2020 by a1batross@a1batrossDeveloper

/api/v1/conversations: empty Account

Environment

  • Installation type (OTP or From Source): sauce
  • Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): latest dev

Bug description

This endpoint always returns empty account in "last_status" field, This is unexpected by the clients and leads to errors.

Also, accounts field of Conversation entity is also empty list. I'm not sure if it should be like that, when conversation have only one participant.

Assignee
Assign to
Time tracking