# Feedback before TableTransforms.jl v1.0

**URL:** <https://discourse.julialang.org/t/feedback-before-tabletransforms-jl-v1-0/80297>\
**Category:** Data\
**Tags:** package, data, dataframes, tables\
**Created:** [April 30, 2022, 3:42pm UTC](https://discourse.julialang.org/t/feedback-before-tabletransforms-jl-v1-0/80297 "2022-04-30T15:42:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [April 30, 2022, 3:42pm UTC](https://discourse.julialang.org/t/feedback-before-tabletransforms-jl-v1-0/80297/1 "2022-04-30T15:42:52Z")

</div>

[TableTransforms.jl](https://github.com/JuliaML/TableTransforms.jl) is ready for a first major release and we would like to ask the community for feedback before moving forward with the registration of v1.0. The API is quite stable and we managed to add [various transforms](https://juliaml.github.io/TableTransforms.jl/stable/transforms/builtin/) during the last month.

> **[GitHub - JuliaML/TableTransforms.jl: Transforms and pipelines with tabular...](https://github.com/JuliaML/TableTransforms.jl)**
>
> Transforms and pipelines with tabular data in Julia - GitHub - JuliaML/TableTransforms.jl: Transforms and pipelines with tabular data in Julia

I would like to thank @eliascarv for his amazing work polishing type instability issues, adding laziness to Select/Reject transforms and many other features. Also, @jafar.isbarov for his first open-source contributions ❤

We are happy to add more transforms to the list, review PRs and consider different design choices that do not affect the end-user interface. Contributions are very welcome.

---

<div class="post-metadata">

**Author:** ![nalimilan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nalimilan/32/147_2.png) [@nalimilan](https://discourse.julialang.org/u/nalimilan)\
**Post date:** [May 3, 2022, 4:12pm UTC](https://discourse.julialang.org/t/feedback-before-tabletransforms-jl-v1-0/80297/2 "2022-05-03T16:12:04Z")

</div>

Nice package!

`apply` and `revert` seem like equivalents of `predict` and `reconstruct` in StatsAPI. The latter has [just been added](https://github.com/JuliaStats/StatsAPI.jl/pull/12) so that MultivariateStats can implement it for things like PCA.

FWIW, StatsBase [supports a few basic transformations](https://juliastats.org/StatsBase.jl/latest/transformations/) but applied to matrices rather than tables, using `standardize` or `fit` with `transform`.

Cc: @wildart

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [May 3, 2022, 4:33pm UTC](https://discourse.julialang.org/t/feedback-before-tabletransforms-jl-v1-0/80297/3 "2022-05-03T16:33:06Z")

</div>

Thank you @nalimilan for the feedback 🙂 We adopted the `apply/revert` naming convention to move away from the statistics jargon since we plan to add different kinds of transforms. We also restricted ourselves to Tables.jl inputs because the lack of variable names with matrices makes the API low-level and cumbersome to work with in practice, e.g. `dim=1` or `dim=2` and `names=[:a,:b,...]` everywhere.