Consider adding a column for each field specified in the fields parameter

[ledell]

The PR which was just merged which adds the fields parameter to find_groups() will add the extra fields to the list (raw data), but the user still has to extract those fields and add them as extra columns to the returned tibble. Should we just add those fields automatically as columns, since it's almost 100% likely that the user will want to do that anyway, since they are explicitly requesting that data?

The other thing I was considering, if we do this, is to make the fields parameter more generic (possibly rename to extra_fields) and then we could allow the user to specify which extra fields they want to add to the returned tibble as extra columns. In this case, those fields could just be extra ones that we already have in the default resource raw list object but are not exposed as columns by default, or they could be the extra ones that must be passed via the API "fields" parameter to the /find/groups endpoint.

Lastly, since it seems like a lot of the endpoints support the "fields" parameter, we could consider adding this functionality to all of the functions. e.g. get_members()

[ledell]

If you have thoughts on this @benubah @RickPack please let me know!

[maelle]

Making the extra fields columns sounds like a good diea to me.

@ledell could you actually open one issue for each of your good ideas?