[bug/proposal] for boolean prop type and enabled enableImplicitConversion flag

[ruscon]

version: "class-transformer": "0.2.3"

example:

import 'reflect-metadata';
import { Expose, plainToClass } from 'class-transformer';

class TestClass {
    @Expose()
    prop: boolean;
}

console.log(plainToClass(TestClass, {
    prop: 'false',
}, {
    enableImplicitConversion: true,
}));

returned: TestClass { prop: true }
expected: TestClass { prop: false }

proposal:
if value === 'true' || value === true || value === 1 || value === '1' then true
otherwise false

somethink like ths:

import { Transform } from 'class-transformer';

export function ToBoolean(): (target: any, key: string) => void {
    return Transform((value: any) => value === 'true' || value === true || value === 1 || value === '1');
}

[joeloudjinz]

Looks like we have the same issue.
see my SOF question

[dsbert]

This issue also means @IsBoolean is useless since any value can be transformed to a boolean.

[adzamkomladev]

Since this is still open, is there any work around?

[ruscon]

@adzamkomladev I'm still waiting for an answer from the developer on how it should work

[leepood]

same problem here

[mostafa-hz]

This issue also means @IsBoolean is useless since any value can be transformed to a boolean.

Until the issue gets fixed, I'm using this approach to handle it:

// ...

@IsBoolean()
@Transform(it => {
  switch (it) {
    case 'true':
      return true;
    case 'false':
      return false;
    default:
      return it;
  }
})
verified!: boolean;

// ...

[karam94]

Same problem here... I have a DTO with a boolean type on it, but I can't actually treat it like a boolean because at runtime it has type string everywhere...

[numToStr]

The shortest version I can think of

import { Transform } from "class-transformer";

export function ToBoolean() {
    return Transform(v => ["1", 1, "true", true].includes(v));
}

[DanielLoyAugmedix]

@numToStr I think this is rather misguided as it will convert all objects not in the set ["1", 1, "true", true] to false. I think this is far too broad a definition for type coercion.

[NoNameProvided]

Hi all!

You can see some comments about this on #334 and #363. In short Boolean('false') == true so the library behaves as expected. We still need some discussion about the correct approach, most probably we will add a custom flag for this.

[davidoween]

I have same problem :(

any solution?

[NoNameProvided]

A tracking issue has been created for this at #550. If you have any feedback regarding the feature, please leave it there.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.