JuliaAI / JuliaAI/MLJModelInterface.jl
Get rid of separate `metadata_pkg`
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I don't understand why we need a separate metadata_pkg when we have metadata_model, as both take a model type as first argument. We should just move all the traits into the latter.
I was recently confused to find is_wrapper trait, in metadata_pkg, before I realised "pkg" does not necessarily mean global to the package, despite the name.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names metadata_pkg, metadata_model, and the is_wrapper trait but no files or tests. Begin by locating those definitions and inventorying the traits in metadata_pkg; done means the traits are consolidated under metadata_model and the separate metadata_pkg is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100