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.

Sign up for GitHub

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

Jump to bottom

Support for wasUnset flag in changes #4

Open
HeikoKlare opened this issue Sep 9, 2017 · 0 comments
Open

Support for wasUnset flag in changes #4

HeikoKlare opened this issue Sep 9, 2017 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@HeikoKlare
Copy link
Contributor

We do only record and apply unsets forward. Nevertheless, it is also necessary to know if a features was unset before a change to be able to correctly apply a change backwards. The addition changes have an appropriate wasSet flag, which is currently not used.
@HeikoKlare HeikoKlare added the enhancement New feature or request label Mar 6, 2018
@HeikoKlare HeikoKlare transferred this issue from vitruv-tools/Vitruv Jun 20, 2022
@TomWerm TomWerm added the bug Something isn't working label Mar 20, 2023
@JanWittler JanWittler mentioned this issue Jul 4, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@HeikoKlare @TomWerm