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
Setting optional values to nil doesn't work #119
Comments
The The correct solution here is to add an |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here I have some option that defaults to 1, but is optional.
Why would explicitly setting an optional to
nil
make it reset to the default? Isn't that whatreset()
is for? Logically it would make sense to have an option that has a default value, but can also be turned off.I tried with an Enum:
But this fails as it doesn't conform to
Defaults.Serializable
.Is there no way to have both a default key, but also retain the ability to set it to nil?
The text was updated successfully, but these errors were encountered: