Brandon Greenwell

I think the way to go is to redefine the **workflows** method using something similar to below: ```r vi.workflow

But part of me thinks it would be best to just remove the `vi.workflow()` method all together and simply encourage (e.g., through the docs) to extract the fit first and...

Thanks @topepo, happy to evolve **vip** to work better with the **tidymodels** ecosystem, so your and @juliasilge's input are extremely appreciated. I'm also planning on removing the **plyr** dependency in...

@juliasilge and @topepo, I've got a fix (not sure why I was making it more complicated than it needed to be). Just needed to move the `"workflow"` method from `vi()`...

Issue should be fixed @juliasilge; let me know if you find the time to test and I'll keep the issue open in the mean time. I just pushed @topepo's workflow...

Hey @juliasilge, good call out. I've thought about this a little bit in the past. I toyed with the idea of checking a sample of the predictions, but I'm not...

Hi @vnijs thank you for posting your issue with a reproducible example! I actually don't see any evidence of a practically meaningful interaction effect (at least as far as the...

I'm not up to speed on {workflows} yet, but if I understand it correctly, this has always been possible in `vi_permute()`, `vi_firm()` (which evolved from the older `vi_pdp()` and `vi_ice()`),...

@topepo, does [your recent PR](https://github.com/koalaverse/vip/pull/128) address this particular issue?

Also, what should be returned? A tibble with one column for every feature and one row for every observation (i.e., wide format)?