mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #1129] [FEATURE REQUEST] Addition of Boolean type extra attribute #401
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#401
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @serghidalg on GitHub (Mar 20, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1129
Motivation
Since 0.6 release, custom attributes have been of great use for many users. I think it would be easy enough to allow a new type of attribute of Boolean type.
Describe the solution you'd like
Integration of custom attributes with Boolean types for users and groups.
Describe alternatives you've considered
I guess String type could be used for those kind of integrations (with "True" or "False") but that may not be so simple for some users and maybe if they are allowed to self edit such attribute they won't know what to add.
Additional context

The feature should be added to the list here and when editing such attribute a checkbox should trigger a change in value.
Thanks for the great work and creating such an amazing project!
@nitnelave commented on GitHub (Mar 20, 2025):
Would it be okay to use an integer instead, with values 1 or 0?
I agree that it's not the best representation and a boolean type would be better. For the record, I'm accepting this feature request as a "we should do this", but given the limited dev time we have, it won't be worked on for a long while (unless you do it yourself, in which case I can help guide you)
@serghidalg commented on GitHub (Mar 20, 2025):
I am afraid I know nothing about Rust and I also find myself quite limited in time, so adding this as a future feature sounds good.
Sorry that I can't help in this occasion :(
And also thanks for the swift response