-
Notifications
You must be signed in to change notification settings - Fork 147
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$i references #131
Comments
Can you provide an example of what you mean? |
Here's an example of the type of json I'm working with and was serialized with fastJson. Take note of the Field GenerailizedType, it is made up of EnumElement which has a nested EnumClass both have two fields Key and Numerator. You appear to be referencing redundant entries because they have similar field settings. So in some cases you list the actual types and their fields and other times you reference them with "$i" : a value. Note in the json below I placed a comment as to the two examples of what I'm talking about, so if you use it you'll have to remove those comments. `{
], |
Do you have any ideas on how to do the dictionary transform without having to use the assemblies? When I go through your code you start to use things like BuildGenericTypeLookups, BuildArrayTypeLookup abd BuildLookUp which all require the Type. I want to get a field value pair listing that uses a string name for type and all the type's properties as field value pairs. This way I can do searches for data without having to require the assemblies and all of its dependencies. I'm sure I'm not the only one that needs such a listing. When the json is just a POCO that's simple you don't use the $i references. Appreciate any help with this, thx. Frank |
|
I need a object type return that is similar to the JSON.Parse method where I don't use a type to get a listing of the json objects and values. Many of the object type values are stored as references in the "$i" value . When you deserialize to a type those are stored in the _cirrev dictionary. Is there a method that can do that already and if not what features of fastJson could I use to resolve the "$i"s?
The text was updated successfully, but these errors were encountered: