Hi,
I have an issue where the non-safe getter is being cached and then when I need the safe version the cache returns the non-safe.
i.e.
First call results in:
second call that needs the safe version gets the above instead of:
This is entirely in kendo code and appears to be caused by having both a grid with (aggregates) and chart on the same page. Both use separate datasources, but contain similar data where the value is a complex object.
The first call to the getter appears to be from the grid datasource running the aggregation (stack trace attached).
Firstly, should the cache not take the safe flag into account? I would consider it a bug that it doesn't.
Secondly, is there a workaround I can use to fix the cache so that the safe version is returned?
I am currently using Kendo UI v2014.1.528 though could update to the latest if it would resolve.
Thanks
Euan
I have an issue where the non-safe getter is being cached and then when I need the safe version the cache returns the non-safe.
i.e.
First call results in:
return
d.c1661059794
return
((d.c1661059794 || {}).value)
This is entirely in kendo code and appears to be caused by having both a grid with (aggregates) and chart on the same page. Both use separate datasources, but contain similar data where the value is a complex object.
The first call to the getter appears to be from the grid datasource running the aggregation (stack trace attached).
Firstly, should the cache not take the safe flag into account? I would consider it a bug that it doesn't.
Secondly, is there a workaround I can use to fix the cache so that the safe version is returned?
I am currently using Kendo UI v2014.1.528 though could update to the latest if it would resolve.
Thanks
Euan