ash-project / ash-project/ash_phoenix
Add Multitenancy Support to ash_phoenix.gen.live & ash_phoenix.gen.html
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 164
- Forks
- 103
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 2
Description
Currently, mix ash_phoenix.gen.live does not natively support multitenancy. For users building SaaS applications with Ash and AshPostgres, handling multitenancy requires manual intervention.
Generated LiveView pages do not automatically respect tenant context, requiring additional modifications to:
• Ensure LiveView sessions and queries include tenant information.
• Modify mount/3 in generated LiveViews to retrieve and apply the correct tenant.
• Adjust the router to properly assign tenants for multitenant-aware resources.
Without first-class support for multitenancy in ash_phoenix.gen.live, developers need to manually patch these issues every time they generate a new resource.
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 the ash_phoenix.gen.live and ash_phoenix.gen.html generators, then inspect generated mount/3 functions, LiveView sessions and queries, and the router behavior described in the issue. Done means generated pages carry the correct tenant context without manual patches, including tenant-aware resource routing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100