What parts of MLJBase should be reexported in MLJ

[vollmersj]

I noticed StaticTransformer has remainded in MLJBase whereas as all other transformer moved to MLJModels. So if you do

using MLJ
using MLJModels

you still dont have access to StatiticTransformer. This could be simply fixed with export in MLJ.jl

[juliohm]

This reflects are more serious issue with export conventions. We should probably use Reexport.jl to reexport all submodules names automatically. See GeoStats.jl for reference. The @reexport macro reexports all exported names in the submodules.

…

On Fri, Feb 28, 2020, 13:04 vollmersj ***@***.***> wrote: I noticed StaticTransformer has remainded in MLJBase whereas as all other transformer moved to MLJModels. So if you do using MLJ using MLJModels you still dont have access to StatiticTransformer. This could be simply fixed with export in MLJ.jl — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#462?email_source=notifications&email_token=AAZQW3NWN4I5AHKAF66FZCTRFEYYRA5CNFSM4K5TDA3KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IRE6I3A>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZQW3LEY4AF4TQX7S4TDODRFEYYRANCNFSM4K5TDA3A> .

[ablaom]

@sjvollmer StaticTransformer is no longer meant for general use. Use Static instead.

Sorry the docs are bit buried at https://alan-turing-institute.github.io/MLJ.jl/dev/composing_models/#Static-operations-on-nodes-1 but #393 should fix this.

@juliohm I don't believe we just re-export every submodule method, so this is not a simple refactor.