We have special logic in the repo tooling that allows rfw to opt some files out of autoformatting. That dates to when flutter/flutter wasn't autoformatted because Hixie didn't think the autoformatter did a good enough job with Flutter code, and so he didn't want it enforced on rfw.
Now that flutter/flutter uses autoformatting everywhere, I think we should remove the opt-out logic, and autoformat those files. It's not quite that easy though, because there are annotations used by custom logic in the coverage regression detector in rfw's custom_tests.sh, and the formatter moves some of those comments in a way that makes the script think coverage has regressed. We'll need to revisit the logic of that coverage detection.
We have special logic in the repo tooling that allows
rfwto opt some files out of autoformatting. That dates to when flutter/flutter wasn't autoformatted because Hixie didn't think the autoformatter did a good enough job with Flutter code, and so he didn't want it enforced onrfw.Now that flutter/flutter uses autoformatting everywhere, I think we should remove the opt-out logic, and autoformat those files. It's not quite that easy though, because there are annotations used by custom logic in the coverage regression detector in
rfw'scustom_tests.sh, and the formatter moves some of those comments in a way that makes the script think coverage has regressed. We'll need to revisit the logic of that coverage detection.