-
Notifications
You must be signed in to change notification settings - Fork 62
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
Non-working example of how we could expose chunk boundaries #20
Conversation
Current coverage is 100% (diff: 100%)@@ master #20 diff @@
===================================
Files 20 20
Lines 869 876 +7
Methods 0 0
Messages 0 0
Branches 169 169
===================================
+ Hits 869 876 +7
Misses 0 0
Partials 0 0
|
Ok @njsmith, here's the necessary extra patches to get this to look something like sensible. Before I go on to write the other ancillary stuff, do you think this approach seems acceptable? If you do, would you like me to also write some narrative documentation about how to never ever use this for anything, and also to write up a changelog entry? |
This all looks sensible, yeah. And yes please to both. We don't have On Nov 3, 2016 9:38 AM, "Cory Benfield" notifications@github.com wrote:
|
GitHub seems to be super confused: there don't appear to be conflicts in |
See gh-19