fix(auth): store Bluesky avatar in preferences instead of photo field #455
+381
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The photo field is a FileEntity relation (integer FK), not a URL string. Bluesky avatars are now correctly stored in preferences.bluesky.avatar where the frontend already looks for them via useAvatarUrl composable. Changes: - Pass avatar URL through auth flow to validateSocialLogin - Store avatar in preferences.bluesky.avatar for new Bluesky users - Update avatar in preferences when existing user logs in with new avatar - Add tests for avatar storage in preferences
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
photofield is aFileEntityrelation (integer FK), not a URL stringpreferences.bluesky.avatarwhere the frontend'suseAvatarUrlcomposable already looks for themChanges
validateSocialLoginpreferences.bluesky.avatarfor new Bluesky usersTest plan