Details
-
Type:
Task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.3.7
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
Description
The documentation page for remoteFunction should more explicitly define the differences between using this tag from a GSP compared to code.
For example, the documentation says:
"method (optional) - The method to use the execute the call (defaults to "post", specified in 'options' array)"
Note that it says "specified in the 'options' array." However, the correct usage from a GSP is to define an attribute for the method, like this:
<g:remoteFunction controller="activity" action="history" method="GET"/>
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits
Burt Beckwith
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Workflow | jira [ 39836 ] | Grails [ 41532 ] |
Burt Beckwith
made changes -
| Workflow | Grails [ 41532 ] | Copy of Grails [ 48957 ] |
Burt Beckwith
made changes -
| Workflow | Copy of Grails [ 48957 ] | Grails [ 56367 ] |
Peter Ledbrook
made changes -
| Assignee | Peter Ledbrook [ pledbrook ] |
Burt Beckwith
made changes -
| Workflow | Grails [ 56367 ] | Grails2 [ 63901 ] |
Burt Beckwith
made changes -
| Workflow | Grails2 [ 63901 ] | jira [ 77131 ] |
Burt Beckwith
made changes -
| Workflow | jira [ 77131 ] | Grails2 [ 85613 ] |
Peter Ledbrook
made changes -
| Last Reviewed | 01/Jan/10 |
Peter Ledbrook
made changes -
| Workflow | Grails2 [ 85613 ] | jira [ 94013 ] |
Peter Ledbrook
made changes -
| Workflow | jira [ 94013 ] | Grails2 [ 102166 ] |