Expose digits argument for h_tbl_median_surv

[Copilot]

Pull Request

Description

The h_tbl_median_surv() function hardcoded signif(..., 4) for rounding median survival estimates. Users can now control precision via a digits parameter.

Changes

• h_tbl_median_surv(): Added digits parameter (default: 4) to control signif() precision for median and CI values
• control_surv_med_annot(): Added digits parameter to expose setting via control interface
• g_km(): Passes digits from control_annot_surv_med with %||% 4 fallback for backward compatibility
• Documentation and tests added

Usage

# Via control object in g_km()
g_km(
  df = df,
  variables = variables,
  control_annot_surv_med = control_surv_med_annot(digits = 2)
)

# Direct function call
h_tbl_median_surv(fit_km = fit, digits = 2)

Backward compatible: default value and fallback maintain existing behavior.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Unit Tests Summary

    1 files     85 suites   1m 37s ⏱️
  901 tests   892 ✅   9 💤 0 ❌
2 231 runs  1 520 ✅ 711 💤 0 ❌

Results for commit 344bf69.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Performance Difference

Additional test case details

Test Suite	$Status$	Time on main	$±Time$	Test Case
h_km	👶		$+0.02$	control_surv_med_annot_works_with_custom_digits
h_km	👶		$+0.03$	h_tbl_median_surv_respects_digits_parameter

Results for commit 8e41787

♻️ This comment has been updated with latest results.

[donyunardi]

Hi @shajoezhu

• Should the digit be exposed all the way to the top to g_km? This is the function that's ultimately being used for tm_g_km
• there's no request to address h_km. This seems to be out-of-scope from the intended issue. Or is there any relationship between g_km and h_km?
• CI/CD did not pass, usually we make sure it passed before review.