Skip to content

Conversation

@kaufmo
Copy link
Contributor

@kaufmo kaufmo commented May 15, 2025

this one was merged in a custom branch and never got it into master so new try (#157)

@vr
Copy link

vr commented May 15, 2025

definitely needed 👍

@kaufmo
Copy link
Contributor Author

kaufmo commented May 28, 2025

@DarthSim @dragonsmith can somebody pls take a look here?

@DarthSim
Copy link
Member

Hey @kaufmo!
Please don't rename values. This will break things for everyone who uses them.

@gzigzigzeo
Copy link
Collaborator

As Darthsim mentioned above, though, this approach would break backward compatibility. There’s also #201, which addresses the issue in the same way but without renaming. I appreciate your contribution! At this point, I think the other PR should take precedence. Thank you again for your efforts here.

@gzigzigzeo
Copy link
Collaborator

However, naming here is much more logical

@gzigzigzeo
Copy link
Collaborator

Thank you again for implementing this. I've merged #198, and fixed the naming as you proposed here, with deprecation warning for an old value. Closing this for now.

@gzigzigzeo gzigzigzeo closed this Sep 25, 2025
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.

4 participants