1
99%
main: 100%

Ran 13 Jan 2025 10:37PM UTC

Files 44

Run time 1s

Badge

Embed ▾

Committed 13 Jan 2025 02:37PM UTC coverage: 99.318% (+0.004%) from 99.314%

Job # b87df7204791f041446dcca766380c40ca92284c-PR-72.1

Build Type

Pull #72

github

Committed by

Gazler

Commit Message

Add support for a binary serializer

In some cases, when using Phoenix channels, it is possible to use a
binary serializer. The library already has support for binary messages,
but this is slightly different. With a binary serializer, all messages
can be sent in a binary format, not just individual payloads. This
commit changes the contract for the serializer to allow returning a
binary as before, or the tuple `{:binary, binary}`

In the integration tests, an example binary encoder that uses
`term_to_binary/1` and `binary_to_term/1` is used. The integration tests
are run both against the existing text based serializer, and the
reference binary serializer. The `GoodExample` has been modified to take
a set of options instead of reading them from the config, although a
fallback is used to minimize the number of tests updated.

Pull Request Pull Request #72: Add support for a binary serializer

Run Details

437 of 440 relevant lines covered (99.32%)

52.66 hits per line

NFIBrokerage / slipstream / b87df7204791f041446dcca766380c40ca92284c-PR-72 / 1
99%
main: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job b87df7204791f041446dcca766380c40ca92284c-PR-72.1

NFIBrokerage / slipstream / b87df7204791f041446dcca766380c40ca92284c-PR-72 / 1 99% main: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job b87df7204791f041446dcca766380c40ca92284c-PR-72.1

NFIBrokerage / slipstream / b87df7204791f041446dcca766380c40ca92284c-PR-72 / 1
99%
main: 100%

README BADGES
x