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

ZAP and restyled disagree on styling for src/darwin/Framework/CHIP/zap-generated/MTRClustersObjc.mm #20236

Closed
bzbarsky-apple opened this issue Jul 1, 2022 · 1 comment · Fixed by #23056

Comments

@bzbarsky-apple
Copy link
Contributor

Problem

Ran into this in #20139. Restyled is insisting on putting in a weird linebreak, while the version of clang-format ZAP runs does not. So we can't have a version of the file that passes both the ZAP job and the restyled job.

Proposed Solution

Sort out how to get the two to agree. For now I have whitelisted this file to not be run through restyled.

@bzbarsky-apple
Copy link
Contributor Author

@vivien-apple @woody-apple Any idea why this disagreement?

bzbarsky-apple added a commit to bzbarsky-apple/connectedhomeip that referenced this issue Oct 6, 2022
It looks like the restyle job and the zap job agree on them now, as
long as we avoid the failure case of an input on which running
clang-format once produces different output from running clang-format
twice.

Fixes project-chip#20236
bzbarsky-apple added a commit to bzbarsky-apple/connectedhomeip that referenced this issue Oct 13, 2022
It looks like the restyle job and the zap job agree on them now, as
long as we avoid the failure case of an input on which running
clang-format once produces different output from running clang-format
twice.

Fixes project-chip#20236
bzbarsky-apple added a commit that referenced this issue Oct 14, 2022
It looks like the restyle job and the zap job agree on them now, as
long as we avoid the failure case of an input on which running
clang-format once produces different output from running clang-format
twice.

Fixes #20236
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 a pull request may close this issue.

1 participant