API-wise I think it would make sense to add a `estimate_contrasts()` method to apply to `estimate_slopes()` outputs `estimate_slopes(m) |> estimate_contrasts()` Instead of complexifying the estimate_slopes() itself _Originally posted by @DominiqueMakowski in https://github.com/easystats/modelbased/issues/301#issuecomment-2579571469_ Yes, we would still not recompute from scratch I reckon a pipe workflow would just be syntactic sugar for: ``` estimate_contrasts.estimate_means <- function(x) { model <- extract_model(x) # recompute contrasts estimate_contrasts(model, ...) } ```
Activity
Make functions pipe-friendly