You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
route: yes
model: yes
controller: no
serializer: yes
route: yes
model: yes
controller: yes
serializer: no
The text was updated successfully, but these errors were encountered:
neojp
changed the title
Better errors when accessing a route with controller / serializer
Better errors when accessing a route without controller / serializer
May 19, 2016
neojp
changed the title
Better errors when accessing a route without controller / serializer
Better errors when accessing a route without a controller / serializer
May 19, 2016
We now have the following messages when a file is missing
```
Error: Could not resolve model by name 'user'
Error: Could not resolve controller by name 'users'
Error: Could not resolve serializer by name 'users'
```
Fixespostlight#104
neojp
added a commit
to neojp/lux
that referenced
this issue
May 21, 2016
We now have the following messages when a file is missing
```
Error: Could not resolve model by name 'user'
Error: Could not resolve controller by name 'users'
Error: Could not resolve serializer by name 'users'
```
Fixespostlight#104
…#118)
We now have the following messages when a file is missing
```
Error: Could not resolve model by name 'user'
Error: Could not resolve controller by name 'users'
Error: Could not resolve serializer by name 'users'
```
Fixes#104
The text was updated successfully, but these errors were encountered: