Skip to content
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

fix: Trim containers one level before max_depth #173

Merged
merged 1 commit into from Jan 30, 2019

Conversation

untitaker
Copy link
Member

No description provided.

@codecov-io
Copy link

codecov-io commented Jan 30, 2019

Codecov Report

Merging #173 into release/0.4.8 will increase coverage by 0.01%.
The diff coverage is 84.61%.

Impacted file tree graph

@@                Coverage Diff                @@
##           release/0.4.8     #173      +/-   ##
=================================================
+ Coverage          64.28%   64.29%   +0.01%     
=================================================
  Files                 82       82              
  Lines               8895     8907      +12     
=================================================
+ Hits                5718     5727       +9     
- Misses              3177     3180       +3
Impacted Files Coverage Δ
general/src/store/trimming.rs 93.12% <84.61%> (-0.88%) ⬇️

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 3a452c9...ee3b4f1. Read the comment docs.

@untitaker untitaker merged commit 4ae7b53 into release/0.4.8 Jan 30, 2019
@untitaker untitaker deleted the fix/max-depth-containers branch January 30, 2019 10:30
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.

None yet

3 participants