API support for Jellyfin Guid with dashes

[its-wizza]

Description

Currently, the Seerr API only supports Guids in the "N" format (32 characters, no dashes), while Jellyfin now prefers "proper Guid formatting", which is a Guid with dashes. While Jellyfin seems to use Guids with no dashes by default, from what I can tell it also supports the same queries with dashes as well.

For example,

• Preferred (D type): 6213b704-a0d9-5429-3110-f4d561b0f614
• Not preferred: (N type): 6213b704a0d954293110f4d561b0f614

Seerr should support both formats to allow seamless interaction between Jellyfin and Seerr.

I am not sure the full extent of the impact of this, so I will explain my issue with a use case:

I want to interact with the Seerr API to automatically import a Jellyfin user as soon as they are created. This will allow the user to interact with the Seerr API without having to log in directly via the web interface, or having an administrator manually import them as a Jellyfin user. Therefore, as soon as they exist as a Jellyfin user, they can interact with the Seerr API.

To do this, I planned to use the Jellyfin Webhook plugin which exposes UserId as a variable, however this contains dashes, and due to the primitive nature of the plugin's helpers, I cannot manipulate it to remove dashes. The relevant Seerr API endpoint /import-from-jellyfin seems to only accept Guids with no hyphens.

Maybe there are other ID types in Jellyfin for which this is also relevant.

Desired Behavior

I should be able to call https://seerr.server/api/v1/user/import-from-jellyfin with body:

{
  "jellyfinUserIds": [
    "6213b704-a0d9-5429-3110-f4d561b0f614"
  ]
}

And it work identically to if I call it without hashes in the user IDs.

Additional Context

No response

Search Existing Issues

• Yes, I have searched existing issues.

Code of Conduct

• I agree to follow Seerr's Code of Conduct