mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 00:05:50 +03:00
[PR #1216] [CLOSED] WIP: fix: "Creation date" in user forum is displayed as a date #1186
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#1186
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?
📋 Pull Request Information
Original PR: https://github.com/lldap/lldap/pull/1216
Author: @selfhoster1312
Created: 7/16/2025
Status: ❌ Closed
Base:
main← Head:fix-user-date-field📝 Commits (1)
f596b13fix: "Creation date" in user forum is displayed as a date📊 Changes
1 file changed (+18 additions, -7 deletions)
View changed files
📝
app/src/components/user_details_form.rs(+18 -7)📄 Description
Previously, when clicking on user details as an admin, i would see
creation_datewith the complete stringy timestamp.Now it's displayed as in the user list view:
This is my first time working with graphql/wasm/yew, so i'm having doubts about the proper way to do things.
Usertype is defined as a type alias toget_user_details::GetUserDetailsUserbut i have no idea where this is defined??? is that somehow an alias tolldap_domain::types::User?User::attributesis stringy but i can accessUser::creation_date… for the typed version (i also didn't find a way to reparse an arbitrary Attribute/AttributeValue from the stringy representationattributesin this template whenuser_tableuses typed attributes… is this because of custom extra attributes? or to simplify form/view logic (if so, it doesn't make it easier to read from the outside)I would be happy to contribute documentation if i understand something finally. I will open a separate issue about frontend documentation. 😄
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.