Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use null values when elements get explicitly set to no value #7214

Open
Tracked by #6871
StefanApfel-Bentley opened this issue Oct 1, 2024 · 0 comments
Open
Tracked by #6871
Labels
ecschema Issues related to the various ecschema packages

Comments

@StefanApfel-Bentley
Copy link
Contributor

StefanApfel-Bentley commented Oct 1, 2024

Whenever a schema element has been not set in the source schema, the differences should use null as value. This way, things that hasn't changed remain undefined, while null is telling there was a change, but it unset the value.

There might be a problem with the schema difference bodies, which currently use the SchemaJSON props as content and they don't have null value.

@StefanApfel-Bentley StefanApfel-Bentley added the ecschema Issues related to the various ecschema packages label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ecschema Issues related to the various ecschema packages
Projects
None yet
Development

No branches or pull requests

1 participant