We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using v3.1, tuples do not encode:
iex(1)> Poison.encode({1, 2}) {:error, {:invalid, {1, 2}}}
I think encoding to an array would be more robust. If that is a no-go, documenting the inability to encode tuples would be an improvement.
The text was updated successfully, but these errors were encountered:
Looks like this is applicable to version 4.1 too, any workarounds for this?
Sorry, something went wrong.
No branches or pull requests
Using v3.1, tuples do not encode:
I think encoding to an array would be more robust. If that is a no-go, documenting the inability to encode tuples would be an improvement.
The text was updated successfully, but these errors were encountered: