Tim Lucas

Ooh sounds exciting. I'll keep an eye out.

Yup agree on all. Though it'd be ``` df[, c('longitude', 'latitude')] ``` Possibly a more general test could be a workflow that creates random covariates with awkward names.

There is at least some marine occurrences on GBIF. I don't know if this is new. Also, marine sdms do work, to some extent. I think we're just lacking better...

I guess you should be able to turn it off but I can only think of 1 situation when you'd want it. Running the entire same workflow multiple times to...

As you currently have it, if someone publishes a big workflow and hasn't set the seeds in each model explicitly then other users still can't replicate. I feel like there...

Hmmm. It feels weird having a default number. For example if we just so happen to pick a weird seed for a module, then all analyses could have this weird...

This is partially the same issue as #32.

The only reason I can think of is that it might be best for all module types to have one default argument, a list of all the or bits. This...

I think it simplifies things. The list name will be used a lot, so the shorter the better. Maybe `.data` for the whole list.

Thanks for reporting this! As tidyverse is so common now, this will definitely be a recurring problem. We'll check this out. Actually it might be easiest for us to just...