✨ New NotBlankString.Companion.create* factory functions

[LVMVRQUXL]

📝 Description

We would like to add create* experimental factory functions to the NotBlankString.Companion type for all platforms with the following signature:

fun NotBlankString.Companion.create(value: Any?): NotBlankString
fun NotBlankString.Companion.createOrNull(value: Any?): NotBlankString?

The NotBlankString type being incompatible with Java due to its declaration as inline value class, these functions shouldn't be available for Java users.

✅ Checklist

• Add the create function, document it, test its behavior with Kotlin, update the public API binaries and the unreleased changelog.
• Add the createOrNull function, document it, test its behavior with Kotlin, update the public API binaries and the unreleased changelog.
• Close this issue as completed and update tracking ones if present.

[LVMVRQUXL]

We should wait for the issue #371 to be resolved before implementing this one.

[LVMVRQUXL]

📝 Description

While accepting a nullable object can be useful in some specific situations, it may be confusing for users. Why creating an instance of NotBlankString from null in Kotlin code or in Java code? We don't know.

This is not because we can call the Any?.toString() function that we should do it!

So, we would like to change the type of the value argument from Any? to Any.

fun NotBlankString.Companion.create(value: Any): NotBlankString
fun NotBlankString.Companion.createOrNull(value: Any): NotBlankString?

✅ Checklist

• Update the create function, its Kotlin tests, the public API binaries and the unreleased changelog.
• Update the createOrNull function, its Kotlin tests, the public API binaries and the unreleased changelog.
• Close this issue as completed and update tracking ones if present.

This comment was moved to the #541 issue.