Earth - Anya #34
Open
Earth - Anya #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CheezItMan
reviewed
Nov 23, 2020
There was a problem hiding this comment.
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 | ✔️ |
| 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) | show action if the work exists |
| 10. Verify that the "View all users" page lists no users | users/index.html.erb view. |
| Log in | -- |
| 11. Logging in with a valid username 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 | ✔️ |
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
Well done Anya, you hit all the learning goals here. This is an excellent submission on a challenging project. The only major area for improvement I have for you is to work on using controller filters.
Nice work!
Comment on lines
+2
to
+12
|
|
||
| root to: 'works#homepage' | ||
|
|
||
| get "/users/current", to: "users#current", as: "current_user" | ||
| post '/works/:work_id/upvote', to: 'votes#upvote', as: 'upvote' | ||
|
|
||
| resources :users, only: [:show, :index] | ||
| get "/login", to: "users#login_form", as: "login" | ||
| post "/login", to: "users#login" | ||
| post "/logout", to: "users#logout", as: "logout" | ||
| resources :works |
| @@ -0,0 +1,46 @@ | |||
| class Work < ApplicationRecord | |||
There was a problem hiding this comment.
Outstanding work with the model methods here. I like the use of .order and .where. Oustanding work.
Also good validations.
Comment on lines
+7
to
+21
| def self.vote_count(user) | ||
| if user.nil? | ||
| return nil | ||
| else | ||
| return user.votes.count | ||
| end | ||
| end | ||
|
|
||
| def self.date_joined(user) | ||
| unless user.nil? | ||
| return user.created_at.strftime("%b %d, %Y") | ||
| else | ||
| return nil | ||
| end | ||
| end |
| belongs_to :work, counter_cache: true | ||
| belongs_to :user | ||
|
|
||
| validates :work_id, uniqueness: { scope: :user_id, message: "• user: has already voted for this work" } |
|
|
||
| def show | ||
| id = params[:id] | ||
| @work = Work.find_by(id: id) |
There was a problem hiding this comment.
What about if this work doesn't exist?
| expect(work.valid?).must_equal true | ||
| end | ||
|
|
||
| it "doesn't need a category" do |
There was a problem hiding this comment.
I think you should test validations you have and not worry about the validations you do not have.
| end | ||
| end | ||
|
|
||
| describe "top_ten" do |
| </tr> | ||
|
|
||
| <% if @users.nil? || @users.length.zero? %> | ||
| <p>No <%= category %> in the system.</p> |
There was a problem hiding this comment.
Maybe you meant this:
Suggested change
| <p>No <%= category %> in the system.</p> | |
| <p>No users in the system.</p> |
| <h2>User Summary: <%= @user.name %></h2> | ||
| <p>Joined site: <%= User.date_joined(@user) %></p> | ||
|
|
||
| <%= render partial: "table", locals: { category: "votes", action_name: @user } %> |
Comment on lines
+20
to
+22
| <%= render partial: "top_ten", locals: { category: "movie" } %> | ||
| <%= render partial: "top_ten", locals: { category: "book" } %> | ||
| <%= render partial: "top_ten", locals: { category: "album" } %> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Media Ranker
Congratulations! You're submitting your assignment!
Comprehension Questions
sessionandflash? What is the difference between them?Assignment Submission: Media Ranker
Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions.
Reflection
sessionandflash? What is the difference between them?