fix: accept both binary and list schema keys - #22
Open
Taure wants to merge 1 commit into
Open
Conversation
jesse expects list strings for schema keys, but Nova routes typically use binaries. Add ensure_list/1 to convert binary schema locations before passing to jesse:validate and jesse:add_schema.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
jesse expects list strings for schema keys, but Nova routes typically use binaries (e.g.
~"schemas/user.json"). This causes afunction_clausecrash injesse_database:load/1when the schema location is a binary.Add
ensure_list/1to convert binary schema locations before passing tojesse:validateandjesse:add_schema.Test plan