Opened 13 years ago
Closed 12 years ago
#6793 closed defect (fixed)
dojo.xhr docs need some love
Reported by: | Adam Peller | Owned by: | dylan |
---|---|---|---|
Priority: | high | Milestone: | 1.2 |
Component: | General | Version: | 1.1.0 |
Keywords: | Cc: | Neil Roberts, Tom Trenka | |
Blocked By: | Blocking: |
Description
some of the ioargs aren't even parsing. "the error function will be called in an error case" -- it might help to describe what an error case is.
Change History (11)
comment:1 Changed 13 years ago by
Cc: | Neil Roberts Tom Trenka added |
---|
comment:2 Changed 13 years ago by
Milestone: | → 1.2 |
---|
comment:3 Changed 13 years ago by
comment:4 Changed 13 years ago by
Owner: | changed from anonymous to dylan |
---|---|
Status: | new → assigned |
I've added info. about the error case.
The parsing part of this bug appears to be fixed (though not yet live on api.dojotoolkit.org).
Neil, are the args defined property for the error function?
comment:5 Changed 13 years ago by
comment:6 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:7 Changed 13 years ago by
comment:8 Changed 13 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
we should probably see this running in api.dtk.org before we close. Also, I think we still need more detail, like information on the callback args (see TODOC)
comment:9 Changed 13 years ago by
comment:10 Changed 13 years ago by
comment:11 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Resolved to my satisfaction thanks to Neil's recent work ( see http://api-staging.dojotoolkit.org/dojo.xhr ).
Note: See
TracTickets for help on using
tickets.
The description that looks like a function is obviously throwing off the parser. Can the doc syntax be such that there is no ambiguity here, or is this a doc parser bug? Also, how would one properly define the function args of the function callbacks here?