Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
all: use Go standard spelling for acronyms #6353
Conversation
rogpeppe
changed the title from
all: use Go standard spelling for acronyms API and NUMA
to
all: use Go standard spelling for acronyms
Sep 29, 2016
|
For reviewers understandably wanting to be careful that the public API hasn't changed,
|
|
I have also verified that nothing in the API has changed with my jujuapidoc tool.
That would have also included parts of the API defined outside the apiserver hierarchy if they had changed. |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
rogpeppe commentedSep 29, 2016
•
Edited 1 time
-
rogpeppe
Sep 29, 2016
The code base is currently inconsistent about whether to use
"Api" or "API", or "Numa" or "NUMA", etc.
This PR changes the code to use the standard Go convention of
capitalising the whole acronym when the first letter is capital.
We've done this for API, NUMA, HTTPS, HTTP, FTP and URL.
It's almost entirely mechanical (the only manual change was in
cmd/modelcmd/base.go where there was an instance variable
named modelApi but a method named modelAPI.
There are some external packages that could also benefit
from this change (notably github.com/juju/utils/proxy).