You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for other standard system value types -- Guid and DateTime, for
example -- is not presently handled within the library. The current
practice is to add support for these types in usage of the library, i.e.
add a guid to a JSONValueCollection as a JSONStringValue.
There is a convenience factor in having a default handling for certain
types, but there also needs to be a way to override the default handling.
For instance, the guid can also be handled as a byte array, which would
emit different JSON output vs. handling as a string.
Support needs to be added to allow default json formatting as well as a
capacity to override json formatting.
Original issue reported on code.google.com by jeff.rod...@gmail.com on 30 Jul 2007 at 5:46
The text was updated successfully, but these errors were encountered:
Exploring different ways for this to be implemented in a pluggable way for
inheritors
to expand. At present, I'm exploring a system involving an ICustomFormatter
interface
(http://msdn2.microsoft.com/en-us/library/system.icustomformatter(vs.80).aspx),
where
the base JSONValue objects would utilize objects implementing ICustomFormatter
to
handle rendering.
This would allow for a pluggable format, but would also increase complexity of
the
underlying objects. This complexity is valuable to those who use JSONReflector,
which would most likely require rendering control for those types not
represented in
the base JSONSharp library.
More later....
Original comment by jeff.rod...@gmail.com on 3 Aug 2007 at 5:45
Original issue reported on code.google.com by
jeff.rod...@gmail.com
on 30 Jul 2007 at 5:46The text was updated successfully, but these errors were encountered: