mirror of
1
Fork 0
forgejo/tests/integration/migration-test
Giteabot b272224918
Preserve BOM in web editor (#28935) (#28959)
Backport #28935 by @silverwind

The `ToUTF8*` functions were stripping BOM, while BOM is actually valid
in UTF8, so the stripping must be optional depending on use case. This
does:

- Add a options struct to all `ToUTF8*` functions, that by default will
strip BOM to preserve existing behaviour
- Remove `ToUTF8` function, it was dead code
- Rename `ToUTF8WithErr` to `ToUTF8`
- Preserve BOM in Monaco Editor
- Remove a unnecessary newline in the textarea value. Browsers did
ignore it, it seems but it's better not to rely on this behaviour.

Fixes: https://github.com/go-gitea/gitea/issues/28743
Related: https://github.com/go-gitea/gitea/issues/6716 which seems to
have once introduced a mechanism that strips and re-adds the BOM, but
from what I can tell, this mechanism was removed at some point after
that PR.

Co-authored-by: silverwind <me@silverwind.io>
(cherry picked from commit b8e6cffd31)
2024-01-31 14:18:26 +01:00
..
forgejo-v1.19.0.mysql.sql.gz [DB] run all Forgejo migrations in integration tests 2023-11-13 12:33:48 +01:00
forgejo-v1.19.0.postgres.sql.gz [DB] run all Forgejo migrations in integration tests 2023-11-13 12:33:48 +01:00
forgejo-v1.19.0.sqlite3.sql.gz [DB] run all Forgejo migrations in integration tests 2023-11-13 12:33:48 +01:00
gitea-v1.6.4.mssql.sql.gz
gitea-v1.6.4.mysql.sql.gz
gitea-v1.6.4.postgres.sql.gz
gitea-v1.6.4.sqlite3.sql.gz
gitea-v1.7.0.mssql.sql.gz
gitea-v1.7.0.mysql.sql.gz
gitea-v1.7.0.postgres.sql.gz
gitea-v1.7.0.sqlite3.sql.gz
migration_test.go Preserve BOM in web editor (#28935) (#28959) 2024-01-31 14:18:26 +01:00