Hi,
Problem description:
I have a singular problem related to an extjs customized vertical stacked graph, where the legend title and yField is the property name field.
I generate a dynamic graph with a reconfigurable store. At init and refresh the graph build/redraw itself with a ExtDirectMethodType.STORE_READ with a ExtDirectStoreReadResult which the result is like List<Map<String, Object>> result = Lists.newArrayList(); and a MetaData metaData and data built on the fly.
That was working wonderfully, no troubles so far.
The problem rose when users suddenly decided to change the name to a double name with space (previously it was a concise single string alpha).
Suddenly, I faced a Json parse error on extjs side because the engine cannot parse a
{...
hello world: 'guten tag'
...}
as a property field name.
So my question/request/enhancement would be to force the wrapping of the property name quoted with single quote or double quote, would it make sense and have some value for the library?
I did have a look on Jackson and there are some stuff which would be possible to do, but I don't want to do on a global basis by tweaking Jackson2ObjectMapperFactoryBean or your JsonHandler permanently.
I would rather for that unique case force the property name wrapping by quote by introduce a localized mixin eventually.
My concern is to not burden EDS library with some if then else in the serialization step for a case that so far no one has met.
For moment I will overwrite in camel case the property name which could on arrival be unwrapped (possible after a successful parsing and a hook in the store event metachange hopefully).
What do you think?
Thanks in advance,
Hi,
Problem description:
I have a singular problem related to an extjs customized vertical stacked graph, where the legend title and yField is the property name field.
I generate a dynamic graph with a reconfigurable store. At init and refresh the graph build/redraw itself with a ExtDirectMethodType.STORE_READ with a ExtDirectStoreReadResult which the result is like List<Map<String, Object>> result = Lists.newArrayList(); and a MetaData metaData and data built on the fly.
That was working wonderfully, no troubles so far.
The problem rose when users suddenly decided to change the name to a double name with space (previously it was a concise single string alpha).
Suddenly, I faced a Json parse error on extjs side because the engine cannot parse a
{...
hello world: 'guten tag'
...}
as a property field name.
So my question/request/enhancement would be to force the wrapping of the property name quoted with single quote or double quote, would it make sense and have some value for the library?
I did have a look on Jackson and there are some stuff which would be possible to do, but I don't want to do on a global basis by tweaking Jackson2ObjectMapperFactoryBean or your JsonHandler permanently.
I would rather for that unique case force the property name wrapping by quote by introduce a localized mixin eventually.
My concern is to not burden EDS library with some if then else in the serialization step for a case that so far no one has met.
For moment I will overwrite in camel case the property name which could on arrival be unwrapped (possible after a successful parsing and a hook in the store event metachange hopefully).
What do you think?
Thanks in advance,