Issue informative warning if user tries to use `evaluate!(::MLJModel, ...)` instead of `evaluate(::MLJModel, ...)`.
Open
Nobody has claimed this yet.
easy
good first issue
- Dominant language
- Julia
- Stars
- 163
- Forks
- 46
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 5
Description
This issue has no description.
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
Start by locating the definitions or entry points for evaluate and evaluate! in MLJBase.jl. Check how calls to the two APIs are currently handled, then verify that using evaluate! with an MLJModel produces an informative warning directing users to evaluate instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100