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

Time- Mair H #32

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

Time- Mair H #32

wants to merge 46 commits into from

Conversation

mheshmati-tech
Copy link

Media Ranker

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a custom model method you wrote. Rendering the list of works in a descending order depending on their vote count was a custom model method. I also wrote a custom method for top_ten work so that media with no vote would not be rendered.
Describe how you approached testing that model method. What edge cases did you come up with? To not include a media with no votes, to render a list in a descending fashion depending on the vote count, and to show the media with the highest votes of all. My method will handle ties by picking the first one on the list.
What are session and flash? What is the difference between them? Session keeps track of the user and their session, this will 'follow' the user, know the state of the user (logged in or not), and capable of verifying if a certain action is permitted depending on the user's session status. Flash on the other hand only lasts for one HTTP request so is not appropriate for usage when tracking a user's activity, only when verifying an action that needs a single request.
What was one thing that you gained more clarity on through this assignment? SQL and the underlying data-structures that Rails operates on.
What is the Heroku URL of your deployed application? https://coolest-media-ranker-ever.herokuapp.com/

… partial rendering to render the edit form to user.
…t the relationship between the three models/controllers
@CheezItMan
Copy link

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 ✔️, blank unless they have votes
2. Can go into a work's show page ✔️
3. Verify unable to vote on a work, and get a flash message ✔️
4. Can edit this work successfully, and get a flash message ✔️
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 ✔️
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) ✔️, produces a 404 message, but a blank white screen, a redirect would be better.
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 ✔️
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 ✔️
3. Practices git with at least 25 small commits and meaningful commit messages ✔️

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 ✔️
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 ⚠ see my comments for more opportunities for partial views.
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 ✔️
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 ✔️

Testing Rails Apps

Criteria yes/no
14. There are valid fixtures files used for users, votes, and works ✔️
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 ✔️

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
Elegant/Clever
Descriptive/Readable
Concise
Logical/Organized

Summary

This is very well done you hit the main learning goals using session and models with relationships. You also have good model tests. You are missing most controller tests and have a few bugs (see my comments). However you're doing very well.

it "can return the page if the user is logged in" do
login()

get current_user_path

Choose a reason for hiding this comment

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

Just noting this test is failing because the view is using the wrong variable name.

@@ -0,0 +1 @@
<h2> Current user is <%= @user.name %></h2>

Choose a reason for hiding this comment

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

Suggested change
<h2> Current user is <%= @user.name %></h2>
<h2> Current user is <%= @logged_user.name %></h2>

post "/logout", to: "users#logout", as: "logout"
get "/users/current", to: "users#current", as: "current_user"

resources :votes, only: [:create]

Choose a reason for hiding this comment

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

I would suggest nesting this route under works, so that you have the work_id in the route.

belongs_to :user
belongs_to :work

validates :work_id, uniqueness: { scope: :user_id }

Choose a reason for hiding this comment

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

👍

end

def self.movies
return Work.where(category: "movie").sort_by { |book| book.votes.count }.reverse

Choose a reason for hiding this comment

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

Just noting these solutions are better using the database functions like .order or .where etc. It's much more efficient to let Postgres do the sorting and filtering for you before Rails gets the list. This works at present, but won't scale well.


if @user.nil?
#New User
@user = User.create(name: params[:user][:name])

Choose a reason for hiding this comment

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

Suggested change
@user = User.create(name: params[:user][:name])
@user = User.create(username: params[:user][:name])

def find_work
@work = Work.find_by(id: params[:id])
if @work.nil?
head :not_found

Choose a reason for hiding this comment

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

I strongly suggest you use a redirect instead of head because it's a bad user experience to present the user with a blank white screen.

require "test_helper"

describe HomepagesController do
# it "does a thing" do

Choose a reason for hiding this comment

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

Just noting no tests here.

require "test_helper"

describe VotesController do
# it "does a thing" do

Choose a reason for hiding this comment

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

Just noting no tests here.

require "test_helper"

describe WorksController do
# it "does a thing" do

Choose a reason for hiding this comment

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

Noting no tests here.

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