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

space - kate #31

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

space - kate #31

wants to merge 48 commits into from

Conversation

katemyer
Copy link

Media Ranker

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a custom model method you wrote. I wrote a custom method in the work and user model to get total votes. For example, in the user model, I filtered the Vote db by work_id = this.id and then returned the count. I was able to then pass this method onto the user view to display the votes.
Describe how you approached testing that model method. What edge cases did you come up with? In order to test this .get_vote_count, I would determine if the user_id matches the self.id. If there's no user, there would not be a count because the database query would not find that user. An edge case would be to test if the user didn't have any votes and it should show empty rather than zero.
What are session and flash? What is the difference between them? Session is a special type of object in a hash form used to keep track of data that does not go away after the next request-response cycle, e.g. information about user when they log in. Flash is also a hash and is a one time message that "flashes" in response to an action a user performed. It could be trying to vote again for a book when they already voted. These messages show up once and then they are gone after the page redirects.
What was one thing that you gained more clarity on through this assignment? I learned that I was able to learn independently more about SQL, joining tables, and how to query. There does not seem to be a standard way to do this and it is all still fuzzy.
What is the Heroku URL of your deployed application? https://mighty-ravine-59897.herokuapp.com/

@kaidamasaki
Copy link

kaidamasaki commented Jun 5, 2020

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 No media without votes appears.
2. Can go into a work's show page ✔️
3. Verify unable to vote on a work, and get a flash message No message.
4. Can edit this work successfully, and get a flash message ✔️ (Flash message says "successfully added" though.)
5. Can go to "View all media" page and see three lists of works, sorted by vote Not 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 No validation errors displayed to the user.
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 "View all users" requires being logged in.
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 Vote are not displayed on 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 No.
5. Routes file shows intention in limiting routes for voting, log-in functionality, and users No. All controllers have all routes.
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 No partials used.
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 No top ten or top media.
10. Some controller, likely the ApplicationController, has a controller filter for finding a logged in user No controller filters.
11. Some controller, likely the WorksController, has a controller filter for finding a work No controller filters.
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 No fixtures.
15. User model has tests with sections on validations (valid and invalid) and relationships (has votes) No test on invalid input or relationships.
16. Vote model has tests with sections on validations (valid and invalid) and relationships (belongs to a user, belongs to a vote) No tests.
17. Work model has tests with sections on validations (valid and invalid) and relationships (has votes) No tests on invalid input or relationships.
18. Work model has tests with a section on all business logic methods in the model, including their edge cases No custom method tests.

Overall Feedback

Overall Feedback Criteria yes/no
Green (Meets/Exceeds Standards) 14+ in Functional Requirements: Manual Testing && 14+ in Code Review
Yellow (Approaches Standards) 12+ in Functional Requirements: Manual Testing && 11+ in Code Review, or the instructor judges that this project needs special attention
Red (Not at Standard) 0-10 in Code Review or 0-11 in Functional Reqs, or assignment is breaking/doesn’t run with less than 5 minutes of debugging, or the instructor judges that this project needs special attention ✔️

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

Copy link

@kaidamasaki kaidamasaki left a comment

Choose a reason for hiding this comment

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

It looks like you had a difficult time with this.

Much of what was here was reasonable but it looks like you ran out of time while working on this. For example your controllers were of rather high quality.

Things to focus on to make sure you solidify your learning based on this are resources, controller filters and model relationships.

app/controllers/homepages_controller.rb Outdated Show resolved Hide resolved
Comment on lines 23 to 30
def edit
@vote = Vote.find_by(id: params[:id])

if @vote.nil?
redirect_to root_path
return
end
end

Choose a reason for hiding this comment

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

Editing a vote is kind of a weird thing to do.

I would have omitted this action.

Copy link
Author

Choose a reason for hiding this comment

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

corrected in file.

Comment on lines 14 to 21
@work = Work.find_by(id: params[:id])
flash[:success] = "#{@work.category} added successfully"
if @work.nil?
flash.now[:error] = "Something happened. Book not added."
render :new, status: :bad_request
#head :not_found
return
end

Choose a reason for hiding this comment

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

I think you meant these flash messages to be in create.

Comment on lines 29 to 34
@work = Work.find_by(id: params[:id])

if @work.nil?
redirect_to root_path
return
end

Choose a reason for hiding this comment

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

This kind of repeated logic should live in a controller filter.

Comment on lines 8 to 12
def get_vote_count
#filter Vote Db by work_id = this.id
count = Vote.where(user_id: self.id).count
return count
end

Choose a reason for hiding this comment

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

This method is equivalent to doing user.votes.count.

Copy link
Author

Choose a reason for hiding this comment

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

updated in code

Comment on lines 20 to 23
if count > 0
return false
end
return true

Choose a reason for hiding this comment

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

Suggested change
if count > 0
return false
end
return true
return count == 0

Copy link
Author

Choose a reason for hiding this comment

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

edited in code

<span class="spotlight__header--prefix">Media Spotlight</span>
<% if @work_spotlight != nil %>
<%= link_to @work_spotlight.title, work_path(@work_spotlight.id), class:'spotlight__link-to' %> by <%= @work_spotlight.creator%>
</h2>

Choose a reason for hiding this comment

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

I don't think you meant to leave this <h2> open if there was no spotlight.

Comment on lines 17 to 18
# Assert
expect(found_user.username).must_equal "test_user"

Choose a reason for hiding this comment

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

Indentation.

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