Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Clarifying the meaning of @ in paramDefaults #8457

Closed
wants to merge 1 commit into from

Conversation

jsdevel
Copy link
Contributor

@jsdevel jsdevel commented Aug 2, 2014

No description provided.

@mary-poppins
Copy link

I'm sorry, but I wasn't able to verify your Contributor License Agreement (CLA) signature. CLA signature is required for any code contributions to AngularJS.

Please sign our CLA and ensure that the CLA signature email address and the email address in this PR's commits match.

If you signed the CLA as a corporation, please let us know the company's name.

Thanks a bunch!

PS: If you signed the CLA in the past then most likely the email addresses don't match. Please sign the CLA again or update the email address in the commit of this PR.
PS2: If you are a Googler, please sign the CLA as well to simplify the CLA verification process.

@mary-poppins
Copy link

CLA signature verified! Thank you!

Someone from the team will now triage your PR and it will be processed based on the determined priority (doc updates and fixes with tests are prioritized over other changes).

@petebacondarwin
Copy link
Contributor

@jsdevel - I have to say that I don't find the rewritten explanation much clearer!

How about:

If the parameter value is prefixed with @ then the value for that parameter will be extracted from the corresponding property on the data object (provided when calling an action method). For example, if the defaultParam object is { someParam: '@someProp' } then the value of someParam will be data.someProp.

@jsdevel
Copy link
Contributor Author

jsdevel commented Aug 2, 2014

@petebacondarwin I like it! Updated the PR.

@jsdevel jsdevel deleted the patch-1 branch August 4, 2014 00:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants