Declare Poison as an optional dependency #144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #98.
Poison is optionally depended on by JOSE.Poison, which is conditionally compiled in. Mix should know that this dependency exists, so that Poison is compiled first, and available during JOSE's compilation when used.
Since Poison is very heavily depended on, I picked the last few major versions to avoid dependency hell when pulling in other libraries that might still depend on an older version. It seems to me that all of these should be compatible with JOSE.Poison, as I only see it depend on Poison.EncodeError which has been around for a long time.