Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
setValues() instead of setValue()#2420
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
xabbuh commentedMar 30, 2013
| Q | A |
|---|---|
| Doc fix? | yes |
| New docs? | no |
| Applies to | all |
| Fixed tickets | #2412 |
| @@ -278,16 +278,17 @@ To work with multi-dimensional fields:: | |||
| <input name="multi[dimensional]" /> | |||
| </form> | |||
| You must specify the fully qualified name of the field:: | |||
| You must specify the values of multi-dimensional fields as arrays itself to | |||
| address which fields' values should be changed:: | |||
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.
I liked the old, short description 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.
I agree that it sounds better but it doesn't really match the code as you do not real fully qualified names. Any propositions for a better phrasing?