-
Notifications
You must be signed in to change notification settings - Fork 44
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
Brenda Rios - API-Muncher - Octos #25
base: master
Are you sure you want to change the base?
Conversation
API MuncherWhat We're Looking For
|
get '/recipes', to: 'recipes#index', as: 'recipes' | ||
|
||
# path for showing details of a recipe | ||
get '/recipes/:uri', to: 'recipes#show', as: 'recipe' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you use resources
for these two routes?
</body> | ||
|
||
<footer> | ||
<h6>Powered by</h6> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The <footer>
(and all content that renders on the page) should go inside the <body>
|
||
describe "#index" do | ||
|
||
it "successfully loads recipe results for any search term" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might also be worthwhile to add some tests around the paging parameters:
- What happens if they're absent?
- Do you get different results when they change?
- What if you send a bogus value, like a negative page number?
API Muncher
Congratulations! You're submitting your assignment!
Comprehension Questions