Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New value features #81

Open
LucieContamin opened this issue Jun 13, 2024 · 0 comments
Open

New value features #81

LucieContamin opened this issue Jun 13, 2024 · 0 comments

Comments

@LucieContamin
Copy link

As I was wondering if it makes sense to allow to set the value type to "numeric".

Currently, "double" or "integer" are the two possibilities, but we can imagine a hub allowing to have some target as integer and/or some others as double and/or integer and it might be easier to allow a "numeric" type column to facilitate with that.

It might also allow some flexibility in case we have submission file with value column in different format and a hub accepting both format:
For example:

> is.numeric(c(5L, 5))
[1] TRUE
> is.double(c(5L, 5))
[1] TRUE
> is.integer(c(5L, 5))
[1] FALSE

> is.integer(5L)
[1] TRUE
> is.double(5L)
[1] FALSE
> is.numeric(5L)
[1] TRUE

> is.integer(5)
[1] FALSE
> is.double(5)
[1] TRUE
> is.numeric(5)
[1] TRUE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant