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.

Sign up for GitHub

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

Jump to bottom

Standardize function and variable naming to underscores #8

Open
jinnatar opened this issue Sep 24, 2017 · 2 comments
Open

Standardize function and variable naming to underscores #8

jinnatar opened this issue Sep 24, 2017 · 2 comments
Assignees
@jinnatar
Labels
enhancement

Comments

@jinnatar
Copy link
Owner

The rename would break compatibility but then again no stability has been yet promised. Need to think about it and get back to this.
@jinnatar jinnatar self-assigned this Sep 24, 2017
@jinnatar
Copy link
Owner Author

Most of the internal renaming is done, mostly just the state option that still has the old name. v0.3 will likely see this along with other compatibility breaks.

@jinnatar jinnatar changed the title remoteToken is confusing, potentially rename to cloud_token Standardize function and variable naming to underscores Mar 4, 2018
@jinnatar
Copy link
Owner Author

jinnatar commented Mar 4, 2018

Still a lot of camelcase in the codebase but slowly I'm fixing them into underscore notation. Fixes are happening among normal development but with v0.3 all deprecated names will be gone, which will incidentally go live when every camelCasing has an underscored replacemnt or alternative. Until then backwards compatibility is maintained at higher abstraction layers (cloud and hub modules) but ignored on lower ones (cloud_api, hub_api).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jinnatar jinnatar

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jinnatar