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

Write specific clang-format rules for Boost and MS UT framework-specific sources #3612

Open
JunielKatarn opened this issue Nov 6, 2019 · 0 comments

Comments

@JunielKatarn
Copy link
Contributor

Current clang-format rules do not play nicely for a set of source files that use on either:

  • Boost.Asio
  • Microsoft Unit Test Framework

We should add/modify a set of format rules so these sources become readable again and stay maintainable.

@JunielKatarn JunielKatarn self-assigned this Nov 6, 2019
@ghost ghost added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Nov 6, 2019
@JunielKatarn JunielKatarn removed the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Nov 6, 2019
@ghost ghost added the Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) label Apr 9, 2020
@chrisglein chrisglein added this to the Backlog milestone Jul 17, 2020
@chrisglein chrisglein removed the Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) label Jul 17, 2020
@ghost ghost added the Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) label Sep 16, 2020
@chrisglein chrisglein added enhancement and removed Invalid Triage https://github.com/microsoft/react-native-windows/wiki/Triage-Process (label applied by bot) labels Sep 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants