Block a user
Create profile page
Update wasm-bindgen to 0.2.95
Fix sidebar component height
Fix missing libretunes-images volume in Docker compose
Standardize all media images
Enable scrolling for home components
eta357
deleted branch 126-create-global-logged-in-user-resource from LibreTunes/LibreTunes
2024-11-03 22:23:35 +00:00
Create global logged in user resource
Create global logged in user resource
Create global logged in user resource
Switch from dotenv to dotenvy
eta357
pushed to 126-create-global-logged-in-user-resource at LibreTunes/LibreTunes
2024-11-03 22:13:59 +00:00
Create global logged in user resource
95-fix-home-screen-account-button-ui
I think you were right originally about having a global logged in user object on the frontend. I can help with the development of this. Adding this would make writing several other pages easier…
95-fix-home-screen-account-button-ui
Turning this into an API endpoint is actually dangerous, as the returned user contains the password hash. This field should be set to None before returning. Although technically the user is only returned if that user has already logged in (and therefore should already know the password), this is still not a good practice. I know I advised you to use this function, but we should add this protection. However this code may change anyways, see my other comment about potentially adding a new function returning an Option<User>.