Conversation
BennyKok
approved these changes
Sep 2, 2025
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.
Here's a concise PR description:
Fix: Add backward compatibility for Clerk's updated user data structure
Problem:
Clerk recently updated their user data structure, replacing the direct
org_idfield with anoobject containing organization data. This broke organization-based functionality across the application.Solution:
Added backward compatibility in the auth middleware to extract
org_idfrom the newo.idstructure when the legacyorg_idfield is not present.Changes:
get_current_user()inauth.pyto handle both old and new Clerk token formatsTesting:
References:
Clerk Auth Object Documentation