Can Convert.ToBoolean supports "1" and "0" values?

[mertmtn]

Existing version of Convert.ToBoolean, only convert from below values.
1,0, "True", "False", "true","false"

We have to apply extra conversion method Convert.ToInt32 in order to convert "1" and "0" to true and false respectively.

Also we have to write extra piece of code like below.
bool boolValue = (convertValue== "1")

Shall we need to improve the method without writing any extension method or using above solutions?
Perhaps, an improvement can be made for the problem as future works

[HaloFour]

Suggestions for API changes should go to the runtime repository.

[mertmtn]

Opened a new issue as your feedback. #86579

[DavidArno]

It would be a huge mistake in my view if the runtime mandated that "1" convert to true. Process return values for example return 0 for success, so I might want that mapped to true.

Such mappings are clearly domain specific and therefore the correct place for them to exist is in your domain logic, not within the BCL.

[FaustVX]

This is valid and non-valid at the same time.
In the .NET world (like most C-based languages), false map to 0 and true to other values.
Look at this code sharplab.io

[mertmtn]

In my opinion, If 1 as integer can convert to true, "1" must be convertible.

[HaloFour]

I disagree. Convertibility is not transitive. I think in cases like this it wades into "truthiness" territory. Like what about "00" or "01" or "2"? I think it opens a can of worms to attempt to interpret a string as a number in order to interpret it as a Boolean.

[cansozbir]

I would expect Convert.ToBoolean to return 0 for an empty string, and 1 for any other string.
This is the current behavior of Python as well.

[mertmtn]

Perhaps, you could consider with another issue because of "empty string" case.

[CyrusNajmabadi]

Moving to runtime.