Skip to content

Tate/fix json client #178

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
Jun 22, 2022
Merged

Tate/fix json client #178

merged 1 commit into from
Jun 22, 2022

Conversation

tatethurston
Copy link
Owner

fixes #176

@tatethurston tatethurston force-pushed the tate/fix-json-client branch 2 times, most recently from 6fea42b to 448c303 Compare June 22, 2022 17:39
@codecov
Copy link

codecov bot commented Jun 22, 2022

Codecov Report

Merging #178 (5c78c22) into main (f9826e2) will increase coverage by 0.76%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #178      +/-   ##
==========================================
+ Coverage   77.81%   78.57%   +0.76%     
==========================================
  Files          14       14              
  Lines        1704     1704              
  Branches      512      512              
==========================================
+ Hits         1326     1339      +13     
+ Misses        365      352      -13     
  Partials       13       13              
Impacted Files Coverage Δ
src/autogenerate/index.ts 97.15% <100.00%> (+0.94%) ⬆️
src/utils.ts 94.11% <0.00%> (+2.78%) ⬆️

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 f9826e2...5c78c22. Read the comment docs.

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

Successfully merging this pull request may close these issues.

JSON Object is not generated correctly for nested proto message
1 participant