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
Where the list of links associated with resources is a key:value pair, some of the keys are base64 encoded and others are not. Example at https://api.spiget.org/v2/resources/269
Either base64 should be always used, or those which need base64 as a way to escape the data should carry a "base64:" tag at the front of the string to denote this.
The text was updated successfully, but these errors were encountered:
I'm currently not sure about how to (if at all) change that without messing with existing clients, I might end up moving all custom (Base64) links to a separate array in the response.
But for now, it's probably easier for you to just check for the 3 definite keys that aren't encoded.
Where the list of links associated with resources is a key:value pair, some of the keys are base64 encoded and others are not. Example at https://api.spiget.org/v2/resources/269
Either base64 should be always used, or those which need base64 as a way to escape the data should carry a "base64:" tag at the front of the string to denote this.
The text was updated successfully, but these errors were encountered: