chore(deps): update dependency protox to v2 #293
+2
−2
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.
This PR contains the following updates:
~> 1.7
->~> 2.0
Release Notes
ahamez/protox (protox)
v2.0.0
Compare Source
Added
schema/0
to access the underlying definition of a message.Changed
Previously, one had to use
:binary.list_to_bin/1
to flatten the iodata and then usebyte_size
, defeating the purpose of having an iodata. Furthermore, it provides a significant performance boost.Protox.decode!
andProtox.decode
no longer raise or return an error if a message don't have all required fields set. We should let the user decide whether it's a problem.InvalidFieldAttribute
toInvalidFieldAttributeError
for consistency.Removed
The implementation was half-baked, it's preferable to have the library focused. Even Google doesn't recommend using JSON: "In short, there are many good reasons why Google prefers to use the standard wire format for virtually everything rather than ProtoJSON format".
:path
option in favor of the already existing:paths
option, which covers the same functionality.:keep_unknown_fields
option (the corresponding--keep-unknown-fields
option for the mix taskprotox.generate
is also removed). They are now always kept.It added complexity to the generation logic while not providing any value as one can simply ignore those fields and as it's mandatory to parse them correctly.
defs/0
(functionality remains available throughschema/0
).field_def/1
(functionality remains available throughschema/0
).file_options/0
(functionality remains available throughschema/0
).required_fields/0
(functionality remains available throughschema/0
).syntax/0
(functionality remains available throughschema/0
).encode/1
from strings for enums.Protox.Encode.encode/1
andProtox.Encode.encode!/1
(functionality remains available in generated modules and inProtox
).v1.7.8
Compare Source
Fixed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.