sf8193
** (Mix) Expected the context, "x", to be a valid module name
Hello!
Having trouble running the phx.gen.html templates. This is the command I’m trying
mix phx.gen.html Shipments shipmentroutes shipmentroute address:string date:string groups_involved:string
with an error message of this
** (Mix) Expected the schema, "shipmentroutes", to be a valid module name
mix phx.gen.html, phx.gen.json and phx.gen.context expect a
context module name, followed by singular and plural names of
the generated resource, ending with any number of attributes.
For example:
mix phx.gen.html Accounts User users name:string
mix phx.gen.json Accounts User users name:string
mix phx.gen.context Accounts User users name:string
The context serves as the API boundary for the given resource.
Multiple resources may belong to a context and a resource may be
split over distinct contexts (such as Accounts.User and Payments.User).
It doesn’t give any reasoning for why it isn’t a valid module name, so I have no idea how to fix this
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
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
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!"
First 4 of 4 Posts
al2o3cr
The validation check that triggers that message is here:
https://github.com/phoenixframework/phoenix/blob/3313bf45a31c34d0455be2400aa2a11461f4228e/lib/mix/phoenix/schema.ex#L59
It’s expecting a singular name that starts with a leading A-Z.
sf8193
Interesting, I ended up changing the name to make it work but still don’t understand why mine wouldn’t work. It does start with the alphabet and it is a singular name no?
benwilson512
A-Zmeans a capital letter not just any letter in the alphabet. Elixir module names must always start with a capital letter (unless explicitly prefixing with:)sf8193
oh god duh-- thanks