Dmitry Jemerov 03fe0f49d1 if there happens to be a line break inside a qualified reference, make sure we add an indent (PY-6359)

2013-11-12 15:28:05 +01:00

..

alignForMethodArguments_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

alignForMethodArguments.py

…

alignInBinaryExpression_after.py

binary expressions in statement parts use continuation indent instead of alignment (PY-8195 #3)

2013-01-29 20:31:10 +01:00

alignInBinaryExpression.py

binary expressions in statement parts use continuation indent instead of alignment (PY-8195 #3)

2013-01-29 20:31:10 +01:00

alignInBinaryExpressions_after.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

alignInBinaryExpressions.py

…

alignInGenerators_after.py

align children of generator expressions (PY-8822)

2013-02-15 19:11:25 +01:00

alignInGenerators.py

align children of generator expressions (PY-8822)

2013-02-15 19:11:25 +01:00

alignInStringLiteral_after.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

alignInStringLiteral.py

…

beforeTopLevelClass_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

beforeTopLevelClass.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

blankLineAfterDecorator_after.py

…

blankLineAfterDecorator.py

…

blankLineAfterImports_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

blankLineAfterImports.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

blankLineAroundClasses_after.py

…

blankLineAroundClasses.py

…

blankLineBeforeFunction_after.py

…

blankLineBeforeFunction.py

…

blankLineBetweenMethods_after.py

…

blankLineBetweenMethods.py

…

comment_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

comment.py

…

commentAfterBlock_after.py

don't indent comments following a statement list (PY-9542)

2013-11-12 15:12:35 +01:00

commentAfterBlock.py

don't indent comments following a statement list (PY-9542)

2013-11-12 15:12:35 +01:00

commentBetweenClasses_after.py

…

commentBetweenClasses.py

…

continuationIndent_after.py

…

continuationIndent.py

…

continuationIndentForCallInStatementPart_after.py

use continuation indent for parameters of call in expression part of control statement (PY-8577)

2013-01-28 16:56:20 +01:00

continuationIndentForCallInStatementPart.py

use continuation indent for parameters of call in expression part of control statement (PY-8577)

2013-01-28 16:56:20 +01:00

dictLiteral_after.py

…

dictLiteral.py

…

fromImportRelative_after.py

…

fromImportRelative.py

…

ifConditionContinuation_after.py

binary expressions in statement parts use continuation indent instead of alignment (PY-8195 #3)

2013-01-29 20:31:10 +01:00

ifConditionContinuation.py

binary expressions in statement parts use continuation indent instead of alignment (PY-8195 #3)

2013-01-29 20:31:10 +01:00

indentAfterBackslash_after.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

indentAfterBackslash.py

auto-indent after backslash (PY-2759)

2013-01-29 20:31:07 +01:00

indentInComprehensions_after.py

option to turn off alignment in collections and comprehensions (PY-8516)

2013-01-28 17:33:13 +01:00

indentInComprehensions.py

option to turn off alignment in collections and comprehensions (PY-8516)

2013-01-28 17:33:13 +01:00

indentInGenerator_after.py

…

indentInGenerator.py

…

indentInNestedCall_after.py

failing test for PY-8195 #4

2013-01-29 20:31:11 +01:00

indentInNestedCall.py

failing test for PY-8195 #4

2013-01-29 20:31:11 +01:00

indentInSlice_after.py

indent, rather than align, child expression of subscription expression (PY-8572)

2013-01-28 16:37:02 +01:00

indentInSlice.py

indent, rather than align, child expression of subscription expression (PY-8572)

2013-01-28 16:37:02 +01:00

inGenerator_after.py

…

inGenerator.py

…

lambdaColon_after.py

…

lambdaColon.py

…

listAssignment_after.py

…

listAssignment.py

…

literals_after.py

…

literals.py

…

longWith_after.py

'with' statement also requires continuation indent for its condition (PY-8743)

2013-02-05 21:35:32 +01:00

longWith.py

'with' statement also requires continuation indent for its condition (PY-8743)

2013-02-05 21:35:32 +01:00

newLineAfterColon_after.py

code style settings to force new line after colon in single-clause and multi-clause compound statements

2013-01-29 20:31:12 +01:00

newLineAfterColon.py

code style settings to force new line after colon in single-clause and multi-clause compound statements

2013-01-29 20:31:12 +01:00

newLineAfterColonMultiClause_after.py

code style settings to force new line after colon in single-clause and multi-clause compound statements

2013-01-29 20:31:12 +01:00

newLineAfterColonMultiClause.py

code style settings to force new line after colon in single-clause and multi-clause compound statements

2013-01-29 20:31:12 +01:00

noAlignForMethodArguments_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

noAlignForMethodArguments.py

…

noWrapBeforeParen_after.py

…

noWrapBeforeParen.py

…

optionalAlignForMethodParameters_after.py

…

optionalAlignForMethodParameters.py

…

pep8ExtraneousWhitespace_after.py

…

pep8ExtraneousWhitespace.py

…

pep8KeywordArguments_after.py

…

pep8KeywordArguments.py

…

pep8Operators_after.py

…

pep8Operators.py

…

setLiteralInArgList_after.py

…

setLiteralInArgList.py

…

spaceAfterComma_after.py

…

spaceAfterComma.py

…

spaceAfterCommaWrappedLine_after.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

spaceAfterCommaWrappedLine.py

…

spaceAfterRelativeImport_after.py

don't delete space between . and 'import' (PY-8112)

2012-12-13 17:03:59 +01:00

spaceAfterRelativeImport.py

don't delete space between . and 'import' (PY-8112)

2012-12-13 17:03:59 +01:00

spaceAfterReturn_after.py

space around more keywords (PY-7863)

2012-10-24 20:03:03 +02:00

spaceAfterReturn.py

space around more keywords (PY-7863)

2012-10-24 20:03:03 +02:00

spaceAroundDot_after.py

…

spaceAroundDot.py

…

spaceAroundKeywords_after.py

more keywords which allow only 1 space around them

2012-10-02 20:04:47 +02:00

spaceAroundKeywords.py

more keywords which allow only 1 space around them

2012-10-02 20:04:47 +02:00

spaceBeforeBackslash_after.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

spaceBeforeBackslash.py

optional space before backslash (on by default) in python code style settings (PY-5674)

2013-01-29 20:31:08 +01:00

spaceInAnnotations_after.py

spacing in py3 annotations (PY-8961)

2013-02-27 14:11:14 +01:00

spaceInAnnotations.py

spacing in py3 annotations (PY-8961)

2013-02-27 14:11:14 +01:00

spaceInMethodDeclaration_after.py

change option "between top-level classes and functions" to "around ...", ensure that we put two lines between import and class (PY-7743)

2012-12-13 20:21:08 +01:00

spaceInMethodDeclaration.py

…

spacesInImportParentheses_after.py

formatter removes spaces in import statement parentheses (PY-11359)

2013-11-11 13:04:28 +01:00

spacesInImportParentheses.py

formatter removes spaces in import statement parentheses (PY-11359)

2013-11-11 13:04:28 +01:00

spaceWithinBraces_after.py

take "space within braces" setting from correct place (PY-8069)

2012-12-13 17:04:00 +01:00

spaceWithinBraces.py

take "space within braces" setting from correct place (PY-8069)

2012-12-13 17:04:00 +01:00

spaceWithinDeclarationParentheses_after.py

"space within method declaration parentheses" code style option (PY-8818)

2013-03-01 15:58:01 +01:00

spaceWithinDeclarationParentheses.py

"space within method declaration parentheses" code style option (PY-8818)

2013-03-01 15:58:01 +01:00

specialSlice_after.py

…

specialSlice.py

…

starArgument_after.py

…

starArgument.py

…

starExpression_after.py

…

starExpression.py

…

tupleAssignment_after.py

…

tupleAssignment.py

…

tupleClosingParen_after.py

don't indent closing paren of tuple (PY-7946)

2012-12-13 17:04:00 +01:00

tupleClosingParen.py

don't indent closing paren of tuple (PY-7946)

2012-12-13 17:04:00 +01:00

tupleInArgList_after.py

…

tupleInArgList.py

…

twoLinesBetweenTopLevelClasses_after.py

…

twoLinesBetweenTopLevelClasses.py

…

twoLinesBetweenTopLevelFunctions_after.py

…

twoLinesBetweenTopLevelFunctions.py

…

unaryMinus_after.py

…

unaryMinus.py

…

wrapAssignment_after.py

don't allow wrapping before operand in slice expression (PY-8572)

2013-01-28 16:24:16 +01:00

wrapAssignment.py

don't allow wrapping before operand in slice expression (PY-8572)

2013-01-28 16:24:16 +01:00

wrapBeforeElse_after.py

pass ASTNode at caret to WhiteSpaceFormattingStrategy.adjustWhiteSpaceIfNecessary(); use that to correctly insert \ when a line break is inserted via the document formatting model (PY-10319)

2013-11-12 13:39:04 +01:00

wrapBeforeElse.py

failing test for PY-10319

2013-11-06 19:17:43 +01:00

wrapDefinitionWithLongLine_after.py

…

wrapDefinitionWithLongLine.py

…

wrapImports_after.py

allow wrapping in imports (PY-9163)

2013-11-12 14:41:26 +01:00

wrapImports.py

allow wrapping in imports (PY-9163)

2013-11-12 14:41:26 +01:00

wrapInBinaryExpression_after.py

surprisingly enough it looks that up until now we didn't have any mechanism for inserting a backslash when Format wraps code in a position where implicit wrap doesn't happen (PY-9032)

2013-03-01 15:58:00 +01:00

wrapInBinaryExpression.py

surprisingly enough it looks that up until now we didn't have any mechanism for inserting a backslash when Format wraps code in a position where implicit wrap doesn't happen (PY-9032)

2013-03-01 15:58:00 +01:00

wrapOnDot_after.py

if there happens to be a line break inside a qualified reference, make sure we add an indent (PY-6359)

2013-11-12 15:28:05 +01:00

wrapOnDot.py

if there happens to be a line break inside a qualified reference, make sure we add an indent (PY-6359)

2013-11-12 15:28:05 +01:00

wrapTuple_after.py

…

wrapTuple.py

…