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

Earth - Schanen #57

Open
wants to merge 26 commits into
base: master
Choose a base branch
from
Open

Earth - Schanen #57

wants to merge 26 commits into from

Conversation

schanenR
Copy link

@schanenR schanenR commented Dec 1, 2020

Media Ranker

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a custom model method you wrote. i wrote a model method to sort works by votes.
Describe how you approached testing that model method. What edge cases did you come up with? I approached testing the model method by considering how the method would handle empty inputs.
What are session and flash? What is the difference between them? Session stores information during a user session and is collected and stored in the users browser. Flash is a message designed to be triggered by specified user behavior.
What was one thing that you gained more clarity on through this assignment? Relationships & fixtures.
What is the Heroku URL of your deployed application? https://media-r-skr.herokuapp.com/

Assignment Submission: Media Ranker

Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions.

Reflection

Prompt Response
What was a custom model method you wrote? What was it responsible for doing?
Describe how you approached testing that model method. What edge cases did you come up with?
What are session and flash? What is the difference between them?
What was one thing that you gained more clarity on through this assignment?
What is the Heroku URL of your deployed application?

Copy link

@CheezItMan CheezItMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Media Ranker

Functional Requirements: Manual Testing

Criteria yes/no
Before logging in --
1. On index page, there are at most 10 pieces of media on three lists, and a Media Spotlight ✔️
2. Can go into a work's show page ✔️
3. Verify unable to vote on a work, and get a flash message ✔️, sort of, see my note in the votescontroller. You're returning prior to redirecting them back. The flash notice shows up later.
4. Can edit this work successfully, and get a flash message ⚠️ No flash notice
5. Can go to "View all media" page and see three lists of works, sorted by vote ✔️?
6. Verify unable to create a new work when the form is empty, and details about the validation errors are visible to the user through a flash message ✔, It prevents the model from being created, but the validation errors are not shown...
7. Can create a new work successfully. Note the URL for this work's show page ✔️
8. Can delete this work successfully ✔️
9. Going back to the URL of this deleted work's show page produces a 404 or some redirect behavior (and does not try to produce a broken view) ✔️, although a flash notice would be nice
10. Verify that the "View all users" page lists no users ✔️
Log in --
11. Logging in with a valid name changes the UI to "Logged in as" and "Logout" buttons ✔️
12. Your username is listed in "View all users" page ✔️
13. Verify that number of votes determines the Media Spotlight ✔️
14. Voting on several different pieces of media affects the "Votes" tables shown in the work's show page and the user's show page ✔️
15. Voting on the same work twice produces an error and flash message, and there is no extra vote ✔️, yes, but it just says it couldn't do it, not why. See my inline notice in the votes controller create method.
Log out --
16. Logging out showed a flash message and changed the UI ✔️
17. Logging in as a new user creates a new user ✔️
18. Logging in as an already existing user has a specific flash message ✔️

Major Learning Goals/Code Review

Criteria yes/no
1. Sees the full development cycle including deployment, and the app is deployed to Heroku ✔️
2. Practices full-stack development and fulfilling story requirements: the styling, look, and feel of the app is similar to the original Media Ranker ⚠️ Still working on styling
3. Practices git with at least 25 small commits and meaningful commit messages ✔️, 26 commits, just enough 😜

Previous Rails learning, Building Complex Model Logic, DRYing up Rails Code

Criteria yes/no
4. Routes file uses resources for works ✔️
5. Routes file shows intention in limiting routes for voting, log-in functionality, and users ✔️, improved!
6. The homepage view, all media view, and new works view use semantic HTML ✔️
7. The homepage view, all media view, and new works view use partials when appropriate ✔️ Sweet!
8. The model for media (likely named work.rb) has_many votes ✔️
9. The model for media has methods to describe business logic, specifically for top ten and top media, possibly also for getting works by some category ⚠️, missing business logic methods
10. Some controller, likely the ApplicationController, has a controller filter for finding a logged in user ✔️
11. Some controller, likely the WorksController, has a controller filter for finding a work ✔️
12. The WorksController uses strong params ✔️
13. The WorksController's code style is clean, and focused on working with requests, responses, params, session, flash ✔️, Greatly improved here. 😻

Testing Rails Apps

Criteria yes/no
14. There are valid fixtures files used for users, votes, and works ✔️ Nice!
15. User model has tests with sections on validations (valid and invalid) and relationships (has votes) ✔️
16. Vote model has tests with sections on validations (valid and invalid) and relationships (belongs to a user, belongs to a vote) ✔️
17. Work model has tests with sections on validations (valid and invalid) and relationships (has votes) ✔️
18. Work model has tests with a section on all business logic methods in the model, including their edge cases ⚠️, no tests for business logic methods, but then you only have one method!

Overall Feedback

Overall Feedback Criteria yes/no
Green (Meets/Exceeds Standards) 14+ in Functional Requirements: Manual Testing && 14+ in Code Review 💚

Code Style Bonus Awards

Was the code particularly impressive in code style for any of these reasons (or more...?)

Quality Yes?
Perfect Indentation
Descriptive/Readable
Logical/Organized

Summary

Nice work Schanen, this is much more solid than the original submission. You had some good tests and good routing. See my inline notes on the way you are sorting the works, but otherwise this is great. Of course your styling is still minimal, but the functionality works.

Comment on lines +5 to +7
resources :works do
resources :votes, only: [:create]
end

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

validates :work_id, :presence => true
validates :user_id, :presence => true

validates_uniqueness_of :user_id, :scope => :work_id, :message => 'user: has already voted for this work'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Awesome!

Comment on lines +17 to +18
return
redirect_back(fallback_location: root_path)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to do the return after you redirect them.

Suggested change
return
redirect_back(fallback_location: root_path)
redirect_back(fallback_location: root_path)
return

redirect_back(fallback_location: root_path)
return
else
flash[:error] = "A problem occurred: Could not upvote"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the darn validation error!

Suggested change
flash[:error] = "A problem occurred: Could not upvote"
flash[:error] = @vote.errors.messages[:user_id].first

t.string "category"
t.datetime "created_at", precision: 6, null: false
t.datetime "updated_at", precision: 6, null: false
t.integer "vote_count", default: 0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like this, you're better off using work.votes.count for the vote-count.

Comment on lines +13 to +15
def self.order_media(category)
where(category: category).order(vote_count: :desc)
end

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works, but it would be easy for the vote_count attribute and the number of votes in the system to get out of alignment. For example someone in the DB deletes a vote, now they don't match!

It's better to rely on votes.count and sort using the relationship with a bit of research.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants