-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Style: update variable name #7755
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
Conversation
``` return createWatcher(vm, expOrFn, cb, options) ``` They are actually the same thing, but use different variable name.
@@ -292,7 +292,7 @@ function initWatch (vm: Component, watch: Object) { | |||
|
|||
function createWatcher ( | |||
vm: Component, | |||
keyOrFn: string | Function, | |||
expOrFn: string | Function, |
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.
It's key path or function, IMO keyOrFn
is better :)
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.
but it's using
return createWatcher(vm, expOrFn, cb, options)
should we change expOrFn
to keyOrFn
, I just get confused when reading the code, exactly the same thing but using different name.
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.
Oops...you are right, it is expOrFn
indeed.😂
@@ -292,7 +292,7 @@ function initWatch (vm: Component, watch: Object) { | |||
|
|||
function createWatcher ( | |||
vm: Component, | |||
keyOrFn: string | Function, | |||
expOrFn: string | Function, |
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.
Oops...you are right, it is expOrFn
indeed.😂
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
They are actually the same thing, but use different variable name.