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.
I started writing a test that needed the
settings
on the artifacts that generatesample_v2.json
and I noticed they weren't there. Did a little housecleaning on the easy to update artifacts (deletingEventListeners
andWebSQL
, finally addingRobotsTxt
andTapTargets
), though at some point (maybe for v5) we should still do a whole-hog update of the artifacts, trace, and devtools log.At that point, surprisingly
sample_v2.json
still wasn't a validLH.Result
, which isn't super important but is kind of annoying. To fix we just had tolhr.configSettings.auditMode
in the cleanup script (just hardcoded totrue
to sidestep the travis issue mentioned in the comment in that file) andArtifacts.MeasureEntry
(which makes up theTiming
artifact) needed to not inherit fromPerformanceEntry
.PerformanceEntry
has atoJSON
method, but when we save artifacts as JSON methods aren't preserved, so the resulting object is no longer aPerformanceEntry
. I just copied the properties over to the type definition rather than inherit now.