supertokens / supertokens/supertokens-python
Fix user type across recipes
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 148
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Right now, The same user type class is used across recipes when the super recipe is using a sub recipe. This results in inconsistency in the type of the user object that is provided to the developer.
We should stick to the same user object type per recipe
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how user types are defined and passed between super recipes and sub recipes in the Python SDK. Reproduce the inconsistency described in the recipe integration path, then identify the expected per-recipe user object type and verify that developers receive that type consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100