I've had issues in the past, and currently, where response validation for some endpoint fails due to differences in the generated spec and new changes introduced from a recent version of plex. The majority of the time, though, these changes are newly added data structures or data structures I've never used within my application so it doesn't matter if they are a expected to be an int but are received as a string (as an example).

Effectively, if I disable response validation by commenting it out within the library code and always return the response I can continue to use plexjs without an issue (I usually check if properties exist within a response regardless of plexjs validation).
Validation is nice to have but it's a hindrance for my project development since its not optional.

Could you please implement a way to disable response validation for certain endpoints (as a request option?) or disable at library level?

This seems to be a reoccuring issue for other users of this library as well:

• postUsersSignInData - SDKValidationError: Response validation failed #33
• Using getLibraryItems always fails #30
• [CRITICAL BUG] Mangled typing breaks numerous functions #23
• [bug] Response validation failed, getMetadata for movie ratingKey #17