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

Report: collapse aggregations when all audits pass #1742

Merged
merged 5 commits into from
Feb 17, 2017

Conversation

ebidel
Copy link
Contributor

@ebidel ebidel commented Feb 17, 2017

R: @patrickhulce @paulirish

In the act of de-cluttering, this PR addresses some of of #1613 and implements the proposed solution in #1613 (comment).

Now, if all audits pass, the entire aggregation is collapsed. If one or more audits fail, the aggregation is opened up.

Before:

screen shot 2017-02-16 at 10 58 53 pm

After:

screen shot 2017-02-16 at 10 40 05 pm

when an audit fail:

screen shot 2017-02-16 at 10 40 24 pm

BTW, the aggregation icons are slightly bigger than the subaudits. I thought the size difference was good but I'm happy to make them all the homogeneous.

  • Aggregations now always create an overall score. Please look over those changes as I may have missed something.
  • Adds css transitions to the details dropdown.
  • @patrickhulce turns out the expectedValues/weights are important and we'll need to use them after all :) aggregate.js uses them to type check and calculate an overall score based on the weights.

@ebidel ebidel changed the title Report: collapse aggregations Report: collapse aggregations when all audits pass Feb 17, 2017
@patrickhulce
Copy link
Collaborator

aggregate.js uses them to type check and calculate an overall score based on the weights

sure it uses them now ;) this is awesome though!

@paulirish
Copy link
Member

Totally on board with the collapsing. Nice.

Regarding scoring, are you saying we'll now have scores for "Best practices" and "fancier stuff"?

@@ -387,11 +412,11 @@
"weight": 1
},
"critical-request-chains": {
"expectedValue": 0,
Copy link
Collaborator

Choose a reason for hiding this comment

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

I thought this one actually was numeric, is it not?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The rawValue that we display is numeric, yes. But we treat the audit as a pass/fail, which means expectedValue needs to be a boolean. AFAICT, expectedValue should really be expectedType.

@ebidel
Copy link
Contributor Author

ebidel commented Feb 17, 2017

Regarding scoring, are you saying we'll now have scores for "Best practices" and "fancier stuff"?

Sorry. There's still only one score in the report (PWA). The difference with this PR is that it calculates an overall score for each subitem. That's not surfaced in the report though.

Before (all overall: 0 for unscored audits):

screen shot 2017-02-17 at 10 02 24 am

Now:

screen shot 2017-02-17 at 10 00 29 am

@patrickhulce
Copy link
Collaborator

After playing with it for a bit, I really like it, but the UX of the cards/boxes could use some work since I don't think it plays well with the collapsed report. Everything is rather succinct and cleanly laid out and the three large uncollapsible boxes really jump out. Can we have those collapse too?

image

@ebidel
Copy link
Contributor Author

ebidel commented Feb 17, 2017

We can play with collapsing those too. Do you think if we use more cards in the report, it'll feel less jarring? Personally I like seeing them b/c it's something other than text.

@patrickhulce
Copy link
Collaborator

Yeah that's a fair point. Right now they just really stick out. If we used them more throughout I'd probably feel differently, but probably need to a strike a balance to prevent wall of text becoming wall of boxes :)

@paulirish
Copy link
Member

Personally I like seeing them b/c it's something other than text.

Agree with that, but if those numbers are in good shape then it's not adding much value to always show them.
(Also maybe the target for each value should be in the card, as I don't know what numbers are good for children and depth)

@ebidel
Copy link
Contributor Author

ebidel commented Feb 17, 2017

Added target vals support to the cards and they're now hidden by default. PTAL.

screen shot 2017-02-17 at 12 40 26 pm

Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

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

SavageJ25 approves this pull request.

I mean... I'm sure he does, too.

(Thx for handling all the back n forth like a pro)

@ebidel
Copy link
Contributor Author

ebidel commented Feb 17, 2017

@patrickhulce you happy too?

@patrickhulce
Copy link
Collaborator

Oh sorry yep!

@ebidel ebidel merged commit 5d662dd into master Feb 17, 2017
@ebidel ebidel deleted the collapsepassingscores branch February 17, 2017 22:08
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.

None yet

3 participants