fix: remove non-ASCII comment to resolve C4819 encoding warning in VS2022 (zh-CN)#1814
fix: remove non-ASCII comment to resolve C4819 encoding warning in VS2022 (zh-CN)#1814potato520hjj wants to merge 1 commit intofacebook:mainfrom
Conversation
…2022 (zh-CN) warning C4819: The file contains a character that cannot be represented in the current code page (936). Save the file in Unicode format to prevent data loss.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @potato520hjj! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
2 participants
warning C4819: The file contains a character that cannot be represented in the current code page (936). Save the file in Unicode format to prevent data loss.