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
For the JSON version of Mentions in processors, all values in the paths are written. When they are read back in, only those paths are used for which the mention is among the Mention's arguments.
This means that a highly desired (by me) round-trip test is not possible:
create mentions
serialized them as json1
read them back in
serialize them as json2
compare json1 and json2
I'm not sure what the paths are supposed to be. If the extra ones are some kind of artifact of Odin processing that can't be avoided, perhaps the ones not among the arguments should be abandoned for the JSON serialization.
I'd appreciate being filled in on how these fields are supposed to be related.
The text was updated successfully, but these errors were encountered:
For the JSON version of Mentions in processors, all values in the paths are written. When they are read back in, only those paths are used for which the mention is among the Mention's arguments.
This means that a highly desired (by me) round-trip test is not possible:
I'm not sure what the paths are supposed to be. If the extra ones are some kind of artifact of Odin processing that can't be avoided, perhaps the ones not among the arguments should be abandoned for the JSON serialization.
I'd appreciate being filled in on how these fields are supposed to be related.
The text was updated successfully, but these errors were encountered: