fix: indentación al insertar código en funciones vacías de Init.php#97
Merged
NeoRazorX merged 1 commit intoJul 13, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug
Al usar comandos que insertan código en
Init.php(por ejemplofsmaker api), si la función destino estaba vacía, las líneas se insertaban sin indentación (pegadas a la columna 0).Por qué sucede
InitEditor::addToFunction()copia la indentación de la última línea de código del cuerpo de la función. Si la función está vacía no hay ninguna línea de la que copiarla, ygetCurrentIndentation()devuelve cadena vacía.Solución
Si la indentación calculada sale vacía, se usa como fallback la indentación de la llave de cierre más un nivel (4 espacios). Verificado con
fsmaker apisobre un plugin de prueba y con la suite de tests en verde.