Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Should we make `bias_correction` argument visible

Open
#421 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r

Research direction

The issue body names no files, tests, or entry points. Start by reading the six-comment discussion on issue #421 and inspect how the bias_correction argument is currently exposed; done requires an agreed decision on whether it should be visible and what behavior or interface change that entails.

Written by the indexing model from the issue text.

Description

What's your opinion :hear_no_evil:

This issue has no description.

Dominant language
R
Stars
263
Forks
22
Avg merge
1h 22m
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from easystats/modelbased

All issues in easystats/modelbased

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.