Opened 14 years ago
Closed 14 years ago
#5810 closed defect (fixed)
combine dojo.cookie and dojo.cookie.useObject
| Reported by: | Adam Peller | Owned by: | Adam Peller |
|---|---|---|---|
| Priority: | high | Milestone: | 1.1 |
| Component: | General | Version: | 1.0 |
| Keywords: | Cc: | jgarfield, dante | |
| Blocked By: | Blocking: |
Description (last modified by )
why not just treat objects in dojo.cookie this way by default? It seems like if an object is passed into the regular dojo.cookie method, it gets serialized with toString() which is usually something worthless like [object Object] and would seem like a bug.
We could do this now for 1.1 and avoid a round of deprecation for useObject.
Change History (4)
comment:1 Changed 14 years ago by
| Cc: | jgarfield dante added |
|---|---|
| Description: | modified (diff) |
comment:2 Changed 14 years ago by
| Owner: | changed from Ben Lowery to Adam Peller |
|---|
comment:3 Changed 14 years ago by
...because, Justin reminds me, you can't know it's an object when you de-serialize without an API hint.
We could combine this into the existing API as an additional (4th?) param? Would mixing it in with 'props' be confusing?
comment:4 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
refs #4969