You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm remaking our new API with CreateAPI and you've left generous comment in our thread jellyfin/jellyfin-sdk-swift#5. Instead of directly using APIClient, I'm making a wrapper JellyfinClient actor that handles the APIClientDelegate creation to inject required headers for the Jellyfin server, among other things for convenience.
Working with this wrapper would just manually require re-declaring the main APIClient interface methods however can cause issues in the future over the evolution of the package. Would creating a protocol for these methods be appropriate for easier implementation of wrappers?
The text was updated successfully, but these errors were encountered:
I'm remaking our new API with CreateAPI and you've left generous comment in our thread jellyfin/jellyfin-sdk-swift#5. Instead of directly using
APIClient
, I'm making a wrapperJellyfinClient
actor that handles theAPIClientDelegate
creation to inject required headers for the Jellyfin server, among other things for convenience.Working with this wrapper would just manually require re-declaring the main
APIClient
interface methods however can cause issues in the future over the evolution of the package. Would creating a protocol for these methods be appropriate for easier implementation of wrappers?The text was updated successfully, but these errors were encountered: