Improve warnings and messages behavior
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 157
- Forks
- 38
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 2
Description
- Go through all warnings and messages in
loocode - Make it easier to suppress warnings and messages with options
- Avoid printing "Warning: " when actually using message()
- Add here a list of all issues which refer to warnings and messages
- Check which warnings and messages come from
posterior, see also https://github.com/stan-dev/posterior/issues/309
Contributor guide
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 inventorying warnings and messages throughout the loo code, then review the related work in PR 290. Check the posterior issue 309 to identify messages originating outside loo. Done means the warning/message cases are cataloged and their suppression options and displayed wording are consistently defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100