Merged
Conversation
Signed-off-by: Roger Barker <roger@pandaswhocode.com>
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
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.
Description
This pull request introduces Gravatar profile picture support, allow users to use their Gravatar avatar as their profile image throughout the application. It adds a
useGravatarboolean field to user profiles, updates the database schema and API documentation, implements Gravatar URL helpers in both backend and frontend, and ensures proper UI integration and security policy updates. The most important changes are grouped below:Backend: Gravatar Support & Data Model Updates
useGravatarboolean field to theUserandUserUpdatestructs ininternal/model/user.go, updated theToUpdateMapmethod, and extended tests to cover this field. [1] [2] [3] [4] [5] [6]internal/gravatar/gravatar.gohelper to generate Gravatar URLs, along with comprehensive unit tests. [1] [2]API & Documentation
api/openapi.yaml) and database schema docs to include theuseGravatarfield, with descriptions and example usage. [1] [2] [3] [4]Frontend: UI and Logic Integration
profile.html,profile.css) for users to enable/disable Gravatar, and updated form handling logic to persist this preference. [1] [2] [3] [4] [5] [6]gravatar.ts), ensuring profile and navigation images use Gravatar when enabled. Updated relevant TypeScript files to use this logic and listen for profile changes. [1] [2] [3] [4] [5] [6]Security and Policy
https://gravatar.comand added corresponding tests to ensure the policy is enforced. [1] [2]Testing
Related Issue(s)