Info for developers

General decisions

I currently have to load pretty much the entire library in one REST call to manually match media. While both Jellyfin and Emby have some (different) filters for your library's content, I found both of them to be pretty wonky at best.

Some parameters seemed to do nothing, others weren't marked as required when they were or results were unpredictable when an invalid value was supplied. This is also one area where Jellyfin and Emby tend to be quite different.

Java/JVM/Spring related decisions

The reason the code looks a little messy and doesn't let Spring's magic run wild with @ConditonalOnProperty is because native images don't support this (yet). Proxies are very limited and creating a @Bean inside a @Config doesn't produce working proxies for things like @PostConstruct and @Cacheable half the time. AOT also doesn't work exactly the same as native image deployment and thus is a lot harder to debug. So if you're seeing unnecessary boilerplate for a Spring application, it's probably required.