Correctly handle "good" code in newline_after_equals.

Author: domdfcoding

formate/mini_hooks.py

@@ -268,15 +268,17 @@ def newline_after_equals(source: str) -> str:
 		token = original_tokens.popleft()
 
 		if token.name == "OP" and token.src == '=':
-			while True:
-
-				# TODO: handle spaces around equals (e.g. in function signature)
-				# Look ahead until there's a non-whitespace token.
-				next_token = original_tokens.popleft()
-				if next_token.name in {"UNIMPORTANT_WS", "NL"}:
-					pass
-				else:
-					break
+			next_token = original_tokens.popleft()
+			if next_token.name == "NL":
+				while True:
+
+					# TODO: handle spaces around equals (e.g. in function signature)
+					# Look ahead until there's a non-whitespace token.
+					next_token = original_tokens.popleft()
+					if next_token.name in {"UNIMPORTANT_WS", "NL"}:
+						pass
+					else:
+						break
 
 			tokens.append(token)
 			tokens.append(next_token)

tests/test_mini_hooks.py

@@ -284,3 +284,10 @@ def test_newline_after_equals(advanced_file_regression: AdvancedFileRegressionFi
 
 	advanced_file_regression.check(newline_after_equals(newline_after_equals_src))
 	assert newline_after_equals(no_newline_after_equals_src) == no_newline_after_equals_src
+
+	src = """
+def foo():
+	directive = SimpleNamespace()
+"""
+
+	assert newline_after_equals(src) == src