bulldog_in_the_dream
I am trying to add a schema and repo functions to an existing context.
I run mix phx.gen.context ExistingContext NewSchema new_schema …
Phoenix picks up that I’m adding to an existing context and asks if I want to proceed, I say yes, everything seems to have been generated fine, I run the migrations. But when I try to compile I get the following error message:
Project.Context.Project.Context.Schema.struct/1 is undefined, cannot expand struct Project.Context.Project.Context.Schema
For some reason Phoenix seems to have duplicated the project/context path and is looking for the schema in a non-existing place. Anyone have an idea what is happening here?
EDIT: I now tried generating just the schema and add code in the context file manually, the problem is the same.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 3 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
achempion
It was because of alias structure. I’ve fixed it for contexts, looks like we should fix it for a schema too. Thank you for a feedback.
bulldog_in_the_dream
We figured it out. We had a schema file inside our Project/Context folder with the same name as Project. When you add to an existing context the code that accesses the repo is added at the bottom of the file, i.e. below the line “alias Project.Context.Project”. For some reason that made Phoenix look in the wrong path. Moving the code above the “alias Project.Context.Project” line fixed it. Don’t know why though.
achempion
Could you please elaborate on shell command you are running to generate context with exact names.
The error trace would definitely help us to better understand your issue.
Thank you.