DataAPI.jl
DataAPI.jl copied to clipboard
JuliaData
A data-focused namespace for packages to share functions
The core metadata methods (`metadata`, `metadata!`, etc.) provide an intuitive method of communicating that a key-value pair provides some information about the instance of the object it is attached to....
If someone has a special need for a function that disregards types, they can make their own wrapper function. The function in DataAPI that's the public function for getting values...
I thought it would be useful to define `rename` and `rename!` in `DataAPI.jl` for functions that achieve purposes similar to what they do for `DataFrames.jl`.
Looking at the concrete implementation of `levels` in `CategoricalArrays`, I see that this function conveniently extracts possible levels from both arrays and individual values: ```julia julia> a = CategoricalArray(["abc", "def",...
When a table does not have `nrow` or `ncol` defined I we can add a description in their docstring what they should return. `nothing` seems a reasonable value.
Currently `describe` contract is that it does pretty print the passed object. The contract does not say what the function returns. I propose that `describe` should keep to print what...
DimensionalData.jl defines a `Selector` abstract type and selectors `Between`, `Near`, `At`, `Where`, and `Contains`. AxisKeys.jl also defines `Selector` and `Near` and `Inervals` selectors (ping @mcabbott) It would be useful to...
I think that all column selectors (other than arrays) should guarantee that the column order in the original table is preserved. One would certainly expect that to be the case...
