Skip to content

Conversation

@javier-godoy
Copy link
Member

Close #56

Copy link
Member

@mlopezFC mlopezFC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be better to clarify this more. As it is with this modification it seems that there is no way of moving forward. Maybe we should explicitly tell that it is allowed to fix the indentation format of the entire file, not just a "partial" fix.

@github-project-automation github-project-automation bot moved this from To Do to In Progress in Flowing Code Addons Jan 5, 2026
@javier-godoy
Copy link
Member Author

The original wording used the word "replace" to describe substitution (essentially, the practice of using a tab character as if it were a certain number of spaces). It was not intended to refer to the act of editing or changing existing code. The new version solves this ambiguity by focusing on consistency throughout the entire file. "Consistency" had appeared as a concept in #46 buf it did not made it word to the previous version of the text.

@javier-godoy javier-godoy requested a review from mlopezFC January 8, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Avoid using whitespace to replace tab characters

3 participants