Add Serialization Configuration for Char and Upgrade Kotlin

[HatoYuze]

fix #53 , #68

✨ Add Serialization Configuration for Char

When creating a Yaml object, you can specify the handling logic for char:

 public enum class CharSerialization {
        SINGLE_QUOTATION,
        DOUBLE_QUOTATION,
        UNICODE_CODE,
        PLAIN,
}

By default, this setting (charSerialization in YamlConfigurationInternal) is set to PLAIN.

Among these, UNICODE_CODE supports the serialization and deserialization of Unicode. You can now handle Char with logic similar to Byte.

Additionally, escaping support for char serialization has been added to prevent certain characters (like '\n', '"', etc.) from being incorrectly input into the content. They will now be escaped with quotes.

The handling logic here is similar to String.

⬆️ Upgrade kotlin

Upgraded the project's kotlin version to 2.0.0. For compatibility, also updated kotlinx.serialization to 1.7.0.

I encountered the same compilation issue as in #72 while attempting the update and fixed it by referring to the corresponding comment.

Therefore, theoretically, this PR should also support the content in #72 and it seems it should fix #67 as well.

[OMGCA]

😊

[Him188]

IIRC class properties are handled differently than top-level values. We should also test serializable classes:

@Serializable
class Container(
    val c: Char,
)

[HatoYuze]

Where should I place this test? Should it be in an existing test class or should I create a new class?

[Him188]

The same file is a good one.

[HatoYuze]

@Him188 Do you think we should support some special codes? For example, should we support deserialization of 'a' from U+0061 (in Unicode number), a (in HTML code), and \0061 (in CSS code)? Or should we add these formats to enum CharSerialization?

[Him188]

If that's in the YAML spec then we are good to support them, if not, then we have to consider whether they are really needed.

This PR is already good enough. Let's focus on fixing the bug first.

[Him188]

LGTM. Thanks!

[HatoYuze]

@Him188 Hey! When do you think this PR can be merged? Thanks!

[Him188]

Thanks for pinging me. Merged.