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

Label and levels improvement #5700

Merged
merged 3 commits into from
Oct 16, 2024

Conversation

JorisGoosen
Copy link
Contributor

I took a bunch of changes @boutinb made in #5630
This also aims to solve the same problems, but I didnt see the need for quite a few changes that were made in that PR.

To keep things trackable I opted to start a bit fresh to avoid messing up the logic.

Co-authored-by: "Bruno Boutin" [email protected]

if there are no 'Label's yet and the user changes the value in the levelseditor to a string some labels will need to be made.
There are some clearly marked functions for this, however, it would always return the last double replaced.
This is usually what is wanted because the other values need not be replaced
but when everything is replaced for convenience the right one should be taken (the one the user edited...)
Not the last one.
@boutinb boutinb merged commit 937d636 into jasp-stats:development Oct 16, 2024
1 check passed
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.

2 participants