Allow custom extensions to use options #683
Closed
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.
Currently the extensions users create themselves cannot access the options passed to the type module. A few of the options, like
:null
and:decode_binary
seem like they should be passed to them. For example, we previously asked users to define their ownltree
andlquery
extensions and our own implementations are using the:decode_binary
option. Also, our own documented example of a custom extension is passed the opts https://hexdocs.pm/postgrex/Postgrex.Extension.html