Skip to content

Consider opennessState on record creation #36

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

Merged
merged 1 commit into from
Oct 11, 2020

Conversation

Lodin
Copy link
Owner

@Lodin Lodin commented Oct 11, 2020

Fixes #35.

This PR fixes the bug when opennessState is not considered during the new record creation which is common case for trees with nodes closed by default.

@Lodin Lodin self-assigned this Oct 11, 2020
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@Lodin Lodin merged commit cb95775 into master Oct 11, 2020
@Lodin Lodin deleted the fix/openness-state-on-creation branch October 11, 2020 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Toggling OpennessState of Items with different nestingLevels must be done sequentially
1 participant