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

tests: update a11y artifacts #9010

Merged
merged 3 commits into from
May 24, 2019
Merged

tests: update a11y artifacts #9010

merged 3 commits into from
May 24, 2019

Conversation

mattzeunert
Copy link
Contributor

@mattzeunert mattzeunert commented May 21, 2019

Summary

Update out of date a11y data. Thought it might be related to #8823, but that PR did update the the artifacts – not sure what changes these are.

Also, when running npm run update:sample-json on master you get the summary: null sample change, which broke the proto tests. Some of the tests already had a beforeAll that fixed that, so moved that beforeAll to be top-level.

@mattzeunert mattzeunert changed the title tests: update a11y artifact tests: update a11y artifacts May 21, 2019
Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

LGTM!

For other reviews, disabling whitespace made this much simpler to look at the actual code changes :)

image

@@ -1115,7 +1115,7 @@
"name": "WordPress"
}
],
"summary": {},
Copy link
Collaborator

Choose a reason for hiding this comment

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

@exterkamp this is expected now, right? I've lost track of all the summary fixes and what's real and what's just tests 😆

Copy link
Member

Choose a reason for hiding this comment

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

No. @brendankenny can get his proto to output {} instead of null, but I can't get mine to, and I guess @mattzeunert can't either. {} should be considered canonical imo, and we need to source out this difference.

Copy link
Collaborator

Choose a reason for hiding this comment

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

make sure you're using the latest protobuf compiler.

Copy link
Member

Choose a reason for hiding this comment

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

I'm on protoc v=3.7.1

I just recompiled from source. I'm going to try to uninstall and reinstall.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ran brew upgrade protobuf to upgrade to 3.7.1 and it works fine for me now.

Copy link
Member

Choose a reason for hiding this comment

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

No. @brendankenny can get his proto to output {} instead of null, but I can't get mine to, and I guess @mattzeunert can't either

I guess @exterkamp now stands alone with his buggy protoc :)

Copy link
Member

@exterkamp exterkamp left a comment

Choose a reason for hiding this comment

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

{} is canonical for empty objects inside a struct like Audit.details and we think upgrading to protoc > 3.7.1 should use {}, but mine doesn't work. So I don't think the 'proto test' should have this conversion code. We need to sort out why ours aren't updating 🤕

@@ -1115,7 +1115,7 @@
"name": "WordPress"
}
],
"summary": {},
Copy link
Member

Choose a reason for hiding this comment

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

No. @brendankenny can get his proto to output {} instead of null, but I can't get mine to, and I guess @mattzeunert can't either. {} should be considered canonical imo, and we need to source out this difference.

@brendankenny
Copy link
Member

Update out-of-date a11y data. Thought it might be related to #8823, but that PR did update the the artifacts – not sure what changes these are.

I think it was mostly from #8373 (with another one from rob that added accesskeys after it has been removed for a little while) and we just never updated the artifacts to match.

@brendankenny brendankenny dismissed exterkamp’s stale review May 24, 2019 23:43

requested proto change fixed, now on vacation :)

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

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

LGTM, thx

@brendankenny brendankenny merged commit cece504 into master May 24, 2019
@brendankenny brendankenny deleted the a11y-artifact-update branch May 24, 2019 23:44
paulirish pushed a commit that referenced this pull request May 28, 2019
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

5 participants