Skip to content

parseInt relies on weird array-to-string coercion in ExternalHdtDatasource #215

Description

@Michiel-VandeVelde

This line passes a regex match result straight into parseInt, which only works because JS auto-converts it to a string behind the scenes. It happens to work now, but it's fragile and easy to break. Want to clean it up (make it explicit) once there's test coverage to be sure nothing depends on the current quirky behavior.

proposed fix:

Image

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