Skip to content

AbstractDumper: decimalPoint fails for pt-BR #46156

@rentalhost

Description

@rentalhost

Symfony version(s) affected

6.0.6

Description

When I dd(12.5), for instance, it is presented like float 12.5,0.

How to reproduce

dd(12.5)

Possible Solution

I can't help with a definitive solution, but I research where the problem is started, and is basically from AbstractDumper constructor, that depends on localeconv() information. The float to string conversion occur in CliDumper::dumpScalar().

For me, it returns:

array (size=18)
  'decimal_point' => string ',' (length=1)
  ...

The float dumper is something like:

            case 'double':
                $style = 'num';

                if (isset($this->styles['float'])) {
                    $style = 'float';
                }

                switch (true) {
                    case \INF === $value:  $value = 'INF'; break;
                    case -\INF === $value: $value = '-INF'; break;
                    case is_nan($value):  $value = 'NAN'; break;
                    default:
                        $value = (string) $value;
                        if (!str_contains($value, $this->decimalPoint)) {
                            $value .= $this->decimalPoint.'0';
                        }
                        break;
                }
                break;

But (string) $value returns string '12.5', that is incompatible to localeconv() info.

My suggestion is detect separator based on a float info directly. For instance:

$this->decimalPoint = str_replace('1', '', (string) 1.1); // => "."

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy