Skip to content

feat: expose deserializer type to allow custom deserializers #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 3, 2020

Conversation

aaron-steinfeld
Copy link
Contributor

Description

Expose the deserializer type to allow registration of custom deserializers via the already public api.

Testing

N/A

Checklist:

  • My changes generate no new warnings
  • [n/a] I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been merged and published in downstream modules

@aaron-steinfeld aaron-steinfeld requested a review from a team as a code owner December 3, 2020 21:58
@codecov
Copy link

codecov bot commented Dec 3, 2020

Codecov Report

Merging #123 (a6c6109) into main (d298c8a) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #123   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           52        52           
  Lines         1429      1429           
  Branches       194       185    -9     
=========================================
  Hits          1429      1429           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d298c8a...a6c6109. Read the comment docs.

@aaron-steinfeld aaron-steinfeld merged commit 266922e into main Dec 3, 2020
@aaron-steinfeld aaron-steinfeld deleted the expose-deserializer-type branch December 3, 2020 22:02
@hypertrace-ci
Copy link

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants