Open jinnatar opened 7 years ago
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.
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).
The rename would break compatibility but then again no stability has been yet promised. Need to think about it and get back to this.