-
Notifications
You must be signed in to change notification settings - Fork 183
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
Separate HTTP.request from Layers.request #469
Conversation
I like the changes here; what's the status @fredrikekre ? I see it's still marked WIP? |
I can update it if you want, wasn't sure the changes were desired and, hence, the draft. This will break packages that insert their own layers, but maybe that is just the AWS packages? Either it needs a breaking new version here or those packages need to be fixed. |
I'd ideally like to get #486 and this PR into a new minor release soon; @fredrikekre, are you able/willing to update here? |
Sure. |
069ea7f
to
67b05a5
Compare
Codecov Report
@@ Coverage Diff @@
## master #469 +/- ##
==========================================
- Coverage 77.53% 69.10% -8.44%
==========================================
Files 36 36
Lines 2333 1780 -553
==========================================
- Hits 1809 1230 -579
- Misses 524 550 +26
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM now. @mattBrzezinski @oxinabox @omus @iamed2 , will this break existing custom layers people have defined elsewhere? If so, we can rename the PR to [BREAKING]
and try to announce the change.
If you remove the |
84aa1c6
to
ce0c1d9
Compare
ce0c1d9
to
55e1328
Compare
@fredrikekre, are you up for updating this PR to get it merged soon for a 1.0 release? |
Included in #789 |
No description provided.