OOR-CORS: rename existing CORS* to Cors* to conform our coding style |
||
Issue descriptionWe have used CORS for naming, e.g. CORSPreflightPolicy, CORSError, and so on. But to conform the chromium coding style guideline, it's better to say CorsPreflightPolicy, CorsError, and so on. Since now we are actively changing CORS related code, we will use existing names for a while, but may use Cors* names on introducing new names. Once OOR-CORS works go to the stable point, we will rename all at once.
,
Nov 21
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Nov 16