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
Question related to User Object's waifu_or_husbando #764
Comments
It's an unintended loophole from shitty freelancer code ;) |
Should the documentation be updated with this detail? |
I don't think there's much value in that. For now, we are focusing on the future main version, the more time we can put into that instead of fixing/documenting not security relevant mistakes from the past, the better. If you want to fix/document it, feel free to create a PR, though. |
Well, if the focus is the new version I think fixing it now isn't important. The documentation is a wiki, so the PR isn't needed, I can just edit it. How about one of those? (I don't know what's the most appropriate)
|
Well you're not actually supposed to be able to have something else, so maybe best to leave it out of the wiki. |
The wiki can document the sorry state of our normalization for now, I don't see any problem with that |
@qgustavor I added the note from your first suggestion to the wiki. Thanks for mentioning this. Eh, at least we support non-binary concepts, I guess 😉 |
The documentation for the User Object says:
By reading it I assumed this value cannot be different from those two values, but it don't happen for this user: https://hummingbird.me/users/AsterPiano (the value is
The duce
).What is the intended behavior, allowing any value (as it's stored as a string) or only those two values?
The text was updated successfully, but these errors were encountered: