Refactor customizeProperty works in order

[seongahjo]

Summary

Refactor customizeProperty works in order

(Optional): Description

ArbitraryBuilder API customizeProperty is affected by order from 1.1.0.

For example, the results of two examples are different.

.setExp(StringValue::value, "abcdef")
.customizeProperty(typedString<String>("value")) {
    it.map { str -> str.substring(0..2) }
}

result -> `abc`

.customizeProperty(typedString<String>("value")) {
    it.filter { value -> value.length > 5 }
}
.setExp(StringValue::value, "fixed")

result -> "fixed"

How Has This Been Tested?

• customizePropertyAfterSet
• customizePropertyIgnoredIfSet

Is the Document updated?

Later