when use partial util type in exactOptionalProperty mode, undefinable property'sx-typia-required tag is incorrect.

[rojiwon123]

In v5.1.5,

when change undefinable property to optional property, x-typia-optional is not changed.

interface IOriginal {
    a?: string | null;
    b: undefined | string;
    c: string;
}

export interface IPartial extends Partial<IOriginal> {}
export interface IRequired extends Required<IPartial> {}

console.log(typia.json.application<[IOriginal, IPartial, IRequired]>().components.schemas);

{
    "IOriginal": {
        "type": "object",
        "properties": {
            "a": {
                "x-typia-required": true,
                "x-typia-optional": true,
                "type": "string",
                "nullable": true
            },
            "b": {
                // I guess, if `x-typia-required` is false, `b` is undefinable.
                "x-typia-required": false,
                "x-typia-optional": false,
                "type": "string"
            },
            "c": {
                "x-typia-required": true,
                "x-typia-optional": false,
                "type": "string"
            }
        },
        "nullable": false,
        "required": ["c"],
        "x-typia-jsDocTags": []
    },
    "IPartial": {
        "type": "object",
        "properties": {
            "a": {
                "x-typia-required": true,
                "x-typia-optional": true,
                "type": "string",
                "nullable": true
            },
            "b": {
                "x-typia-required": false,
                // I think, it is right that `x-typia-optional` is true.
                "x-typia-optional": false,
                "type": "string"
            },
            "c": {
                "x-typia-required": true,
                "x-typia-optional": true,
                "type": "string"
            }
        },
        "nullable": false,
        "x-typia-jsDocTags": []
    },
    "IRequired": {
        "type": "object",
        "properties": {
            "a": {
                "x-typia-required": true,
                "x-typia-optional": false,
                "type": "string",
                "nullable": true
            },
            "b": {
                "x-typia-required": false,
                "x-typia-optional": false,
                "type": "string"
            },
            "c": {
                "x-typia-required": true,
                "x-typia-optional": false,
                "type": "string"
            }
        },
        "nullable": false,
        "required": ["a", "c"],
        "x-typia-jsDocTags": []
    }
}

I guess x-typia-required mean definable property and x-typia-optional mean optional property.

[samchon]

Next version v5.1.6 would be published soon.

[samchon]

Additionally, as issues are being raised one by one, so patch versions are being released repeatedly.

Next time, please report it all at once \o/.

[rojiwon123]

Additionally, as issues are being raised one by one, so patch versions are being released repeatedly.

Next time, please report it all at once \o/.

ok! i'm sorry and thank you :)

[rojiwon123]

Bug description

even if Partial or Required Util Type change property's optional feature, their typia tag x-typia-optional is not changed.

bug condition

• tsconfig exactOptionalProperty mode
• undefinable property
• use Partial util type or Required util type (they change property's optional feature)

test case

export interface IQuery {
    required: string;
    nonRequired: string | undefined;
    optional?: string;
    none?: string | undefined;
}
export interface IPartialQuery extends Partial<IQuery> {}
export interface IRequiredQuery extends Required<IQuery> {}

const app = typia.json.application<[IQuery, IPartialQuery, IRequiredQuery]>();
const result1 = typia.assert<IJsonComponents.IObject>(
    app.components.schemas?.IQuery,
);
const result2 = typia.assert<IJsonComponents.IObject>(
    app.components.schemas?.IPartialQuery,
);
const result3 = typia.assert<IJsonComponents.IObject>(
    app.components.schemas?.IRequiredQuery,
);
console.log(
    "IQuery",
    Object.entries(result1.properties).map(([key, value]) => [
        key,
        value["x-typia-required"],
        value["x-typia-optional"],
    ]),
);
console.log(
    "IPartialQuery",
    Object.entries(result2.properties).map(([key, value]) => [
        key,
        value["x-typia-required"],
        value["x-typia-optional"],
    ]),
);
console.log(
    "IRequiredQuery",
    Object.entries(result3.properties).map(([key, value]) => [
        key,
        value["x-typia-required"],
        value["x-typia-optional"],
    ]),
);

expected

IQuery [
  [ 'required', true, false ],
  [ 'nonRequired', false, false ],
  [ 'optional', true, true ],
  [ 'none', false, true ]
]
IPartialQuery [
  [ 'required', true, true ],
  [ 'nonRequired', false, true ],
  [ 'optional', true, true ],
  [ 'none', false, true ]
]
IRequiredQuery [
  [ 'required', true, false ],
  [ 'nonRequired', false, false ],
  [ 'optional', true, false ],
  [ 'none', false, false ]
]

actual

IQuery [
  [ 'required', true, false ],
  [ 'nonRequired', false, false ],
  [ 'optional', true, true ],
  [ 'none', false, true ]
]
IPartialQuery [
  [ 'required', true, true ],
  [ 'nonRequired', false, `false` ],
  [ 'optional', true, true ],
  [ 'none', false, true ]
]
IRequiredQuery [
  [ 'required', true, false ],
  [ 'nonRequired', false, false ],
  [ 'optional', true, false ],
  [ 'none', false, `true` ]
]

`` is error result!

[rojiwon123]

Additionally, as issues are being raised one by one, so patch versions are being released repeatedly.

Next time, please report it all at once \o/.

I apologize for providing short explanations that led to you performing repetitive tasks.
above comment is detail description of my bug report