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
{{ message }}
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
in the course of comparing data, CRViz adds some utility and marker properties to the supplied datasets such as HASH_KEY, isChanged, etc. These properties should be excluded from the dataset's export function.
Describe your use case
On a re-import these properties are treated in the same way as properties of the original dataset which is undesireable and problematic.
Explain how this feature supports your use case? Other use cases?
It makes more sense to remove them on the output than it does to ignore them on the input in order to preserve compatibility over time.
Additional Info
None.
The text was updated successfully, but these errors were encountered:
After thinking about it i have decided to consolidate all of the properties that CRViz adds into a single subobject that can be removed for export purposes. This effectively namespaces everything out to something like item.CRVIZ.property
Describe the feature you are requesting
in the course of comparing data, CRViz adds some utility and marker properties to the supplied datasets such as HASH_KEY, isChanged, etc. These properties should be excluded from the dataset's export function.
Describe your use case
On a re-import these properties are treated in the same way as properties of the original dataset which is undesireable and problematic.
Explain how this feature supports your use case? Other use cases?
It makes more sense to remove them on the output than it does to ignore them on the input in order to preserve compatibility over time.
Additional Info
None.
The text was updated successfully, but these errors were encountered: