-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Profiler summary #1259
Profiler summary #1259
Conversation
Hello @Borda! Thanks for updating this PR.
Comment last updated at 2020-03-31 11:39:34 UTC |
@jeremyjordan mind have a look at it before finalizing? |
i don't understand the package rename. we went from i like the abstraction over writing the summary more flexibly, however if you're going to rename |
The case with with
It is not renaming at all as it may appear from diff, just adding extra function to generate the string text and so there is no no change for user at all (except before you write it file or console, no always write console and optional file) |
ahh i see the however, i'd say that we should keep the module where it's currently located in |
I agree with @jeremyjordan we need to stop making unnecessary changes to package names @Borda |
This pull request is now in conflict... :( |
Codecov Report
@@ Coverage Diff @@
## master #1259 +/- ##
======================================
- Coverage 92% 92% -0%
======================================
Files 62 62
Lines 3181 3210 +29
======================================
+ Hits 2924 2949 +25
- Misses 257 261 +4 |
This pull request is now in conflict... :( |
This pull request is now in conflict... :( |
@Borda mind submitting a follow-up PR which makes |
I changed it as it was so it is file or info... Or you want to remove info for any case? |
ah i missed that last round of commits, thanks! this looks great. |
* refactor and add types * add Prorfiler summary * fix imports * Revert "refactor and add types" This reverts commit b4c552f * changelog * revert rename * fix test * mute verbose
What does this PR do?
Reaction to #1253. in particular:
debugging
packagePR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃