Are Jellyseerr's Radarr/Sonarr tags compatible with the develop Radarr API tag validation rules? #1942
-
|
Currently, Radarr/Sonarr do not blacklist characters from tags at the API level, only at the GUI level. It seems this was an oversight and not intentional as the upcoming Radarr v6 has recently received a commit that does this validation (and presumably Sonarr will too). Overseerr, the project Jellyseerr is based on, currently puts spaces in the tags it creates for Sonarr/Radarr. For example: myuser - 17. Once this update rolls out to Radarr, this type of tag will not be allowed. I'm curious is Jellyseerr also does this / if an issue should be opened preemptively to fix this. Related links: PS. If someone does open an issue in response to this, please mention the Overseerr issue to link it; it could be useful if this commit is propagated back to Overseerr. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Please see #1913. It's already fixed in the develop branch and will be available in the next version.
You're also confusing Jellyfin and Jellyseerr. |
Beta Was this translation helpful? Give feedback.
Please see #1913. It's already fixed in the develop branch and will be available in the next version.
You're also confusing Jellyfin and Jellyseerr.