fix: escape raw NUL bytes to fix Sonar encoding warning

Browse Source

Four Kotlin sources embedded literal NUL (0x00) bytes, used as string
separators and as literal characters in KDoc comments. A NUL is valid
UTF-8 (U+0000) so decoders accept it, but SonarScanner flags an embedded
NUL in a text source as a file-encoding problem, and git tracked these
files as binary.

...

This commit is contained in:

davotoula

2026-07-01 21:25:27 +02:00

parent d0497eaed7

commit f7dd2c210b

4 changed files with 0 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

amethyst/src/main/java/com/vitorpamplona/amethyst/Amethyst.kt

BIN

Binary file not shown.

amethyst/src/main/java/com/vitorpamplona/amethyst/napplet/DataStoreNappletPermissionStore.kt

BIN

Binary file not shown.

amethyst/src/main/java/com/vitorpamplona/amethyst/napplet/DataStoreNappletStorage.kt

BIN

Binary file not shown.

quartz/src/jvmAndroid/kotlin/com/vitorpamplona/quartz/nip34Git/git/GitObject.kt

BIN

Binary file not shown.