Bump protox from 1.7.2 to 2.0.0

[dependabot]

Bumps protox from 1.7.2 to 2.0.0.

Release notes

Sourced from protox's releases.

v2.0.0

2.0.0

Added

• schema/0 to access the underlying definition of a message.

Changed

• Minimal supported Elixir version is now 1.15.
• BREAKING CHANGE: encoding functions now return the size alongside iodata. Previously, one had to use :binary.list_to_bin/1 to flatten the iodata and then use byte_size, defeating the purpose of having an iodata. Furthermore, it provides a significant performance boost.
• BREAKING CHANGE: Protox.decode! and Protox.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.
• BREAKING CHANGE: Rename InvalidFieldAttribute to InvalidFieldAttributeError for consistency.

Removed

• BREAKING CHANGE: Drop support of JSON encoding and decoding. 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".
• BREAKING CHANGE: Remove :path option in favor of the already existing :paths option, which covers the same functionality.
• BREAKING CHANGE: Remove :keep_unknown_fields option (the corresponding --keep-unknown-fields option for the mix task protox.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.
• BREAKING CHANGE: Remove generated defs/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated field_def/1 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated file_options/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated required_fields/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated syntax/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated encode/1 from strings for enums.
• BREAKING CHANGE: Remove Protox.Encode.encode/1 and Protox.Encode.encode!/1 (functionality remains available in generated modules and in Protox).

v1.7.8

What's Changed

• Fix warnings of unknown JSON modules when a JSON library is not installed

Full Changelog: ahamez/protox@v1.7.7...v1.7.8

v1.7.7

What's Changed

• Fix launch by removing :propcheck from extra applications

Full Changelog: ahamez/protox@v1.7.6...v1.7.7

v1.7.6

What's Changed

• fix: correct the return type for json_decode! by @​squirmy in ahamez/protox#200

New Contributors

• @​squirmy made their first contribution in ahamez/protox#200

Full Changelog: ahamez/protox@v1.7.5...v1.7.6

v1.7.5

... (truncated)

Changelog

Sourced from protox's changelog.

2.0.0

Added

• schema/0 to access the underlying definition of a message.

Changed

• Minimal supported Elixir version is now 1.15.
• BREAKING CHANGE: encoding functions now return the size alongside iodata. Previously, one had to use :binary.list_to_bin/1 to flatten the iodata and then use byte_size, defeating the purpose of having an iodata. Furthermore, it provides a significant performance boost.
• BREAKING CHANGE: Protox.decode! and Protox.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.
• BREAKING CHANGE: Rename InvalidFieldAttribute to InvalidFieldAttributeError for consistency.

Removed

• BREAKING CHANGE: Drop support of JSON encoding and decoding. 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".
• BREAKING CHANGE: Remove :path option in favor of the already existing :paths option, which covers the same functionality.
• BREAKING CHANGE: Remove :keep_unknown_fields option (the corresponding --keep-unknown-fields option for the mix task protox.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.
• BREAKING CHANGE: Remove generated defs/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated field_def/1 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated file_options/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated required_fields/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated syntax/0 (functionality remains available through schema/0).
• BREAKING CHANGE: Remove generated encode/1 from strings for enums.
• BREAKING CHANGE: Remove Protox.Encode.encode/1 and Protox.Encode.encode!/1 (functionality remains available in generated modules and in Protox).

1.7.8

Fixed

• Fix warnings of unknown JSON modules when a JSON library is not installed

1.7.7

Fixed

• Fix launch by removing :propcheck from extra applications

1.7.6

Fixed

• Fix typespecs for JSON decoding (thanks to https://github.com/squirmy)

1.7.5

Changed

• Use origin repository for propchek rather than a fork

... (truncated)

Commits

• b7eeb38 v2.0.0
• 719698d chore(deps-dev): bump quokka from 2.3.1 to 2.4.1
• 025ef5c chore(deps-dev): bump ex_doc from 0.37.2 to 0.37.3
• 15fbfce chore(deps-dev): bump quokka from 2.2.0 to 2.3.1
• affe9af chore(deps-dev): bump quokka from 2.1.0 to 2.2.0
• b847077 chore(deps-dev): bump stream_data from 1.1.2 to 1.1.3
• c6c42c5 style: apply quokka 2.1
• c340ab3 docs: general improvement
• f3a5cf6 docs: document public modules
• 7c57ab8 docs: add a migration guide
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #29.