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
I'm using Groot for quite some time now and lately I have experienced a quite strange problem.
I'm mapping JSON var not_found on a Core Data attribute isNotFound. Within the attached JSON there are 4 line-item entities, two of them with not_found = true and another two with not_found = false. My problem is that all entities are parsed correctly except for the one with id == 504330. Even though its not_found is true it's parsed as false (which is the attribute's default value in Core Data). So it's either not parsed correctly, or not parsed at all. However, object with id == 504333 that also has its not_found set to true is parsed correctly.
I'm using Groot for quite some time now and lately I have experienced a quite strange problem.
I'm mapping JSON var
not_found
on a Core Data attributeisNotFound
. Within the attached JSON there are 4 line-item entities, two of them withnot_found = true
and another two withnot_found = false
. My problem is that all entities are parsed correctly except for the one withid == 504330
. Even though itsnot_found
istrue
it's parsed asfalse
(which is the attribute's default value in Core Data). So it's either not parsed correctly, or not parsed at all. However, object withid == 504333
that also has itsnot_found
set totrue
is parsed correctly.Here's the JSON:
And here's the
isNotFound
Core Data attribute after parsing:The text was updated successfully, but these errors were encountered: