Skip to content

Time - Sharon Cheung#33

Open
sharonkeikei wants to merge 43 commits into
Ada-C13:masterfrom
sharonkeikei:master
Open

Time - Sharon Cheung#33
sharonkeikei wants to merge 43 commits into
Ada-C13:masterfrom
sharonkeikei:master

Conversation

@sharonkeikei

Copy link
Copy Markdown

Media Ranker

Congratulations! You're submitting your assignment!

My ERD for Media Ranker
https://app.lucidchart.com/documents/edit/d5307ecf-19e4-4c50-ad9a-04473b83720c/0_0?beaconFlowId=56D1F03507703A99#?folder_id=home&browser=icon

Comprehension Questions

Question Answer
Describe a custom model method you wrote. I wrote a custom model method for the vote, to check whether there is already an existing vote from the login user for that specific work that they are trying to vote again by returning true or false.
Describe how you approached testing that model method. What edge cases did you come up with? I approached testing the models by thinking of the relationship between different models and how are they related to each other. And also, all the possible ways that a user could use or break the website. I come up with as much edge cases as I could, I tested all the possible way a user would input for their username, their new work forms and how validation would work toward making sure all the attributes are there.
What are session and flash? What is the difference between them? We use 'Flash' message to show user how their request has been successfully processed or failed, while we use 'session' to keep track of who is currently logged in and we can make some pages specific for people that has an account with us. 'Flash' will only last for one request, but 'session' will last as long as the cookies does not expire, or as long as the user is logged in.
What was one thing that you gained more clarity on through this assignment? I gained more clarity on how MVC works and how everything related and work with one another, and where to put the methods in. Also, gaining more clarity on working with database.
What is the Heroku URL of your deployed application? https://sharon-media-ranker.herokuapp.com/

@CheezItMan

Copy link
Copy Markdown

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 ✔️
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 ✔️, but it only shows the 1st validation error.
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) ✔️
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 ⚠ some unused routes etc.
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 ✔️, really good use of partials
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

Nicely done, you hit all the learning goals here. Well done. Excellent work. Take a look at my comments, mostly regarding routes.rb and some other minor issues.

Comment thread config/routes.rb
resources :works do
get '/upvote', to: "votes#upvote", as: 'upvote'
end
resources :users

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Do you need all the users routes?

Comment thread config/routes.rb
post "/login", to: "users#login"
post "/logout", to: "users#logout"

get '/homepages', to: 'homepages#index', as: 'homepages'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

If you have homepages#index as the route route, do you need this?

Comment thread test/models/vote_test.rb
describe 'custom method' do
describe 'self.check_exisiting_vote(current_user_id, work_id)' do

it 'will return true if there is already an exisitng vote for that specific user and work' do

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
it 'will return true if there is already an exisitng vote for that specific user and work' do
it 'will return true if there is already an existing vote for that specific user and work' do

Comment thread app/models/work.rb

def self.sort_by_vote_order
work = Work.all
return work.sort_by{|work| work.votes.count}.reverse

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Just noting that it's more efficient to do this with .order and other methods to have Postgres do the filtering and sorting. Postgres is much better at it.

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