Set default value for an options object#1495
Merged
Merged
Conversation
mrmlnc
force-pushed
the
fix_unchangeable_options
branch
from
October 9, 2020 18:10
5578014 to
5b95af1
Compare
Contributor
Author
|
Looks like CI fails due to last update of node.js. Works fine under |
Collaborator
|
@mrmlnc Can you please open another issue for this? |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
I ran into a problem that after the client extension by the
.extendmethod, theinithook gets anundefinedinstead of an object as options.The following example illustrates the problem.
Looks like a bug, because I see that the
inithook should get anOptionsobject according to the signature in the types.got/source/core/index.ts
Line 103 in 87dadd5
So, this PR fixes the problem. If you accept this change, I can make a backport to the
v11branch.Checklist