API should use a new "SessionInfoDto" type to avoid duplicate types for ClientCapabilities and BaseItem #5551

Closed
opened 2026-02-07 01:55:40 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @nielsvanvelzen on GitHub (Mar 28, 2024).

Currently the OpenAPI specification contains a few duplicate types because we're not using a data transfer object for SessionInfo.

The SessionInfo is "leaked" from the API in a few places:

  • SessionController.getSessions
  • SessionsMessage (in a property)
  • AuthenticationResult (in a property)

These places need to be changed to use a (new) SessionInfoDto type, that uses the proper Dto types for its members. An alternative fix would be to use the dto types in the existing SessionInfo.

Originally created by @nielsvanvelzen on GitHub (Mar 28, 2024). Currently the OpenAPI specification contains a few duplicate types because we're not using a data transfer object for SessionInfo. The SessionInfo is "leaked" from the API in a few places: - SessionController.getSessions - SessionsMessage (in a property) - AuthenticationResult (in a property) These places need to be changed to use a (new) SessionInfoDto type, that uses the proper Dto types for its members. An alternative fix would be to use the dto types in the existing SessionInfo.
OVERLORD added the bugconfirmedstale labels 2026-02-07 01:55:40 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Mar 28, 2024):

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • This bug report was not filed using the issue template.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@jellyfin-bot commented on GitHub (Mar 28, 2024): Hi, it seems like your issue report has the following item(s) that need to be addressed: - This bug report was not filed using the issue template. This is an automated message, currently under testing. Please file an issue [here](https://github.com/jellyfin/jellyfin-triage-scripts/issues) if you encounter any problems.
Author
Owner

@jellyfin-bot commented on GitHub (Jul 27, 2024):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Jul 27, 2024): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#5551