flake8
passed.
JSHint
passed.
Never show the initial status updates entry as being new.
Review Request #9257 — Created Oct. 10, 2017 and submitted
The initial status updates entry on the review request page generally
will accompany the review request when first published, or will appear
shortly after as the result of a call to some external service or tool.
When first shown, it was appearing as new, with that state changing
shortly after when a status update changes. Showing this entry as new
doesn't really benefit anyone, and the jump in newness is a bit weird.
It also just wasn't useful as the newness never represented things like
new reviews from status updates.This change forces the entry to never appear as new. Replises will
continue to appear as new as needed.
Unit tests pass.
Tested that the initial status update entry didn't appear new on
review request creation.
| Description | From | Last Updated |
|---|---|---|
|
As I mentioned in a comment on the test, the superclass has some required args. I think you should probably … |
 david
|
|
|
Should be *args |
david
|
|
|
The superclass implementation requires last_visited and user arguments. I don't think this test is particularly valuable as-written--if the new is_entry_new … |
david
|
-
-
As I mentioned in a comment on the test, the superclass has some required args. I think you should probably include those in the method signature here instead of just catching it with
*args. -
-
The superclass implementation requires
last_visitedanduserarguments. I don't think this test is particularly valuable as-written--if the newis_entry_newfunction didn't exist, this would crash.
