Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Exclude generated properties from exported dataset #238

Closed
rashley-iqt opened this issue Feb 14, 2019 · 1 comment
Closed

Exclude generated properties from exported dataset #238

rashley-iqt opened this issue Feb 14, 2019 · 1 comment
Assignees

Comments

@rashley-iqt
Copy link
Member

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.

@rashley-iqt
Copy link
Member Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants