diff options
author | Nick Guerrera <nicholg@microsoft.com> | 2015-09-23 17:21:09 +0300 |
---|---|---|
committer | Nick Guerrera <nicholg@microsoft.com> | 2015-09-23 17:25:44 +0300 |
commit | d5e2aafc51231e6ff1bd2c08fc619cbd66e56f42 (patch) | |
tree | 64039f3b86674dadbfb655f4e70d741154bf9000 /Documentation/coding-guidelines | |
parent | 907eaa2f77e734486c695c1de193785e9e0a20c8 (diff) |
Tweak and run native code formatting script
* Rename script to format-code.sh to match naming convention of
other shell scripts in the repo.
* Make script work when executed from any working directory.
* Run script to mop up some minor formatting issues that crept in.
Diffstat (limited to 'Documentation/coding-guidelines')
-rw-r--r-- | Documentation/coding-guidelines/coding-style.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/coding-guidelines/coding-style.md b/Documentation/coding-guidelines/coding-style.md index a8127c0a72..e711708ce2 100644 --- a/Documentation/coding-guidelines/coding-style.md +++ b/Documentation/coding-guidelines/coding-style.md @@ -1,7 +1,7 @@ C# Coding Style =============== -For C++ files (*.cpp and *.h), we use clang-format (version 3.6+) to ensure code styling. After changing any Cpp or H file and before merging, be sure to run ./formatCode.sh from within the Native directory; this script will ensure that all native code files adhere to the coding style guidelines. +For C++ files (*.cpp and *.h), we use clang-format (version 3.6+) to ensure code styling. After changing any Cpp or H file and before merging, be sure to run src/Native/format-code.sh; this script will ensure that all native code files adhere to the coding style guidelines. For non code files (xml etc) our current best guidance is consistency. When editing files, keep new code and changes consistent with the style in the files. For new files, it should conform to the style for that component. Last, if there's a completely new component, anything that is reasonably broadly accepted is fine. |