Repository navigation
fix(go): port auth profile and password endpoints from app.ts - #320
Merged
Merged
Conversation
PUT /api/auth/profile (partial profile update with zod-equivalent validation, display_name null coercion, users SSE broadcast) and PUT /api/auth/password (change with current-password check, other sessions invalidated) were never ported: they live in app.ts, which the routes-parity script did not cover. This broke language/profile changes in production (404). Both endpoints ported with round-trip tests, and the parity script now includes app.ts plus MethodFunc registrations, closing the gap (117 routes, full parity).
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.
Production bug: changing language or profile settings returned 404 ("No se ha podido guardar el perfil") because PUT /api/auth/profile and PUT /api/auth/password were never ported - they live in app.ts, which the routes-parity script did not include as a source (it only covered the routes-*.ts files).
Deploy note: this is a server-only fix (binary), no frontend change.