Corrige testes do Pages e persistência ao recarregar - #1
Merged
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
1 participant
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.
A execução do Pages falhava porque um teste substituía o módulo compilado do renderer, cujos exports são transformados no build, e porque o rascunho podia se perder ao recarregar antes do autosave de 250 ms.
A inicialização assíncrona agora tem teste unitário; o editor salva alterações pendentes em pagehide. O workflow verifica pull requests e preserva traces e screenshots quando os testes falham.
Validação local: 18 testes unitários, TypeScript, build estático com 3.013 assets verificados e os três testes de navegador repetidos duas vezes sob /dancer/ (6 passaram). Assets continuam fora do Git.