Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better errors when accessing a route without a controller / serializer #104

Closed
neojp opened this issue May 19, 2016 · 0 comments · Fixed by #118
Closed

Better errors when accessing a route without a controller / serializer #104

neojp opened this issue May 19, 2016 · 0 comments · Fixed by #118
Labels

Comments

@neojp
Copy link
Contributor

neojp commented May 19, 2016

route: yes
model: yes
controller: no
serializer: yes


route: yes
model: yes
controller: yes
serializer: no

@neojp 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 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
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'
```

Fixes postlight#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'
```

Fixes postlight#104
zacharygolba pushed a commit that referenced this issue May 21, 2016
…#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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants