Skip to content

Uniform documentation and behavior for na_str - Can I add a vector? #251

@Melkiades

Description

@Melkiades

@Melkiades on second thought, I think we should make a separate PR to tackle this issue - we have to also consider the fact that users can supply multiple na_str values for multi-value formats (e.g. na_str = c("lo", "hi") for "xx.xx - xx.xx"), which would complicate enabling vector input.

I see! Have you made it already? I think we need to understand how it is exactly applied and uniform that. In other words, we have to see exactly what providing a vector entails. From a user perspective, you would do 3 things: (1) one for all na_str (current default). (2) 2+ for specific formats (how do we select them externally? I do not remember, is na_str working as formats, that you can specify different values with named vectors?) (3) assign them all in order (if less, cycle)

Originally posted by @edelarua @Melkiades in #250 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or requestsmeTracks changes for the sme board

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions