Skip to content

Component properties as double, affected by culture info #276

@Denny09310

Description

@Denny09310

Hi,

Some time ago, I submitted a PR to fix culture-related issues for double properties in components (#200).

I’m now encountering the same problem in other components (e.g., BbResizablePanel). I’m not entirely sure whether the approach used in that PR is the best way to address this across the codebase, as the issue may also affect other components.

Could you please advise if this is the right solution, or if there’s a more consistent approach we should follow?

Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions