massive refactoring to switch from camelCase to snake_case:
historically, Libervia (SàT before) was using camelCase as allowed by PEP8 when using a pre-PEP8 code, to use the same coding style as in Twisted. However, snake_case is more readable and it's better to follow PEP8 best practices, so it has been decided to move on full snake_case. Because Libervia has a huge codebase, this ended with a ugly mix of camelCase and snake_case. To fix that, this patch does a big refactoring by renaming every function and method (including bridge) that are not coming from Twisted or Wokkel, to use fully snake_case. This is a massive change, and may result in some bugs.
This commit is contained in:
parent
d50412c7f7
commit
6a6f15707a
1 changed files with 9945 additions and 9945 deletions
|
|
@ -66,7 +66,7 @@ Display details for merge request with id 456::
|
|||
import
|
||||
======
|
||||
|
||||
Import a merge request into your project. You mainly have to be in the project repository
|
||||
import a merge request into your project. You mainly have to be in the project repository
|
||||
(or specify it using ``-r PATH, --repository PATH``) and to specify the id of the patch to
|
||||
import (using ``-i ITEM, --item ITEM``). The behaviour depends of the type of the patch,
|
||||
for Mercurial, the patch will be imported as `MQ`_ patch.
|
||||
|
|
@ -76,6 +76,6 @@ for Mercurial, the patch will be imported as `MQ`_ patch.
|
|||
example
|
||||
-------
|
||||
|
||||
Import the merge request with id 321::
|
||||
import the merge request with id 321::
|
||||
|
||||
$ li merge-request import -i 321
|
||||
|
|
|
|||
Loading…
Reference in a new issue