Bring xr.align objects specification in line with other top-level functions?

Was wondering if this might be useful given that I ran into this point of confusion. Observing the following argument specifications for various top-level xarray functions:

xarray.align(*objects, join='inner', copy=True, indexes=None, exclude=frozenset())

xarray.concat(objs, dim=None, data_vars='all', coords='different', compat='equals', positions=None, indexers=None, mode=None, concat_over=None)

xarray.concat(objs, dim=None, data_vars='all', coords='different', compat='equals', positions=None, indexers=None, mode=None, concat_over=None)

xarray.merge(objects, compat='no_conflicts', join='outer')

the odd man out here would be xr.align utilizing the *args formulation whereas all the others just take a single objs / objects param, instead. Would it make sense to add functionality to align such that if *args (*objects) is of length 1 and is a list or tuple (or something in this ballpark), you just treat it as the other methods currently operate?

For reference, if you don't notice that align works differently, if you pass an iterable without *args-ifying it, you get this somewhat unhelpful error:

Start by reading the public xarray.align API and comparing its signature and input handling with xarray.concat and xarray.merge. Clarify the intended behavior for a single list or tuple versus the existing argument forms, then verify that the resulting error handling and documented usage match the requested consistency.