31 lines
1.8 KiB
Plaintext
31 lines
1.8 KiB
Plaintext
=== is related to: S1120
|
|
|
|
=== on 20 May 2013, 12:44:05 Fabrice Bellingard wrote:
|
|
Implementation: \http://jira.codehaus.org/browse/SONARJAVA-122
|
|
|
|
=== on 12 Feb 2014, 21:47:06 Freddy Mallet wrote:
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3468 for PHP
|
|
|
|
=== on 9 Mar 2018, 16:27:19 Janos Gyerik wrote:
|
|
Irrelevant for Go, because this rule goes against the recommendation in https://golang.org/doc/effective_go.html#formatting[Effective Go] (_"Use spaces only if you must."_).
|
|
|
|
=== on 28 Oct 2019, 14:16:35 Nicolas Harraudeau wrote:
|
|
Low value rule for python as:
|
|
|
|
* tabs are accepted if the rest of [the code base is already using it](\https://www.python.org/dev/peps/pep-0008/#id18).
|
|
* pycodestyle already supports all PEP8 rules and there is no point for us to reimplement them.
|
|
|
|
=== on 23 Jan 2022, 22:20 JY Cr wrote:
|
|
|
|
Fixing the visual size of the indentations for everyone makes it difficult to read the code for people who need a size adapted to their needs or their context.
|
|
|
|
Indeed, the advantage of tabulation is precisely to make it possible to adapt the readability of the code according to the constraints of the user.
|
|
|
|
This is an fundamental accessibility criterion.
|
|
|
|
In addition, this allows a group of developers, some of whom prefer large indentations, and others, more restrained indentations, to work on the same code base (each configuring according to his needs, on his IDE, the visual size of the desired intentation).
|
|
|
|
Here is an article motivating the deprecation of this rule: https://dev.to/alexandersandberg/why-we-should-default-to-tabs-instead-of-spaces-for-an-accessible-first-environment-101f
|
|
|
|
In order not to go against readability and accessibility aspects, while avoiding problems related to alignment (different concept from indentation), it is preferable to favor "[smart tabs](https://www.emacswiki.org/emacs/SmartTabs) indentation".
|