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
As mentioned in #215, the assert statements take only place in debug mode. Which means, when this library is compiled or run in production, the asserts are simply ignored.
So in order to provide library users a better handling of the spotify API constraints (e.g. number of tracks in a json) when this library is compiled (or in production mode) and without making unnecessary requests, all methods, that have assert statements, should be replaced with ArgumentErrors or similar.
As mentioned in #215, the
assert
statements take only place in debug mode. Which means, when this library is compiled or run in production, the asserts are simply ignored.So in order to provide library users a better handling of the spotify API constraints (e.g. number of tracks in a
json
) when this library is compiled (or in production mode) and without making unnecessary requests, all methods, that haveassert
statements, should be replaced withArgumentError
s or similar.Thanks to @artyuum for pointing this out.
The text was updated successfully, but these errors were encountered: