html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/3596#issuecomment-601282600,https://api.github.com/repos/pydata/xarray/issues/3596,601282600,MDEyOklzc3VlQ29tbWVudDYwMTI4MjYwMA==,5635139,2020-03-19T16:36:55Z,2020-03-19T16:36:55Z,MEMBER,"Thanks @mark-boer ! Must be one of the largest first contributions...

+1 re merge + experimental warning; maybe we should do this more often. Cheers @dcherian ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,532940062
https://github.com/pydata/xarray/pull/3596#issuecomment-598730380,https://api.github.com/repos/pydata/xarray/issues/3596,598730380,MDEyOklzc3VlQ29tbWVudDU5ODczMDM4MA==,5635139,2020-03-13T13:52:13Z,2020-03-13T13:52:13Z,MEMBER,"Agree!

We could add an ""Experimental"" label and then worry less about future changes","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,532940062
https://github.com/pydata/xarray/pull/3596#issuecomment-596837204,https://api.github.com/repos/pydata/xarray/issues/3596,596837204,MDEyOklzc3VlQ29tbWVudDU5NjgzNzIwNA==,5635139,2020-03-10T00:08:11Z,2020-03-10T00:08:11Z,MEMBER,"> In some instances extrapolating all coords, can lead to some unwanted behaviour. Would you suggest we only interpolate the indexes?
> 
> How would we handle unsorted indexes?
> 
> How would we extrapolate all the different kind of indexes, like the MultiIndex or CategoricalIndex?

I agree; I can't see easy solutions to these. If there are evenly spaced indexes (e.g. dates, grids), then it's easy to know what to do. But there are plenty of times it's difficult, if not intractable.

One option to merge something useful without resolving these questions is to return Variables only and label this method experimental. I think this is immediately useful for the cases where these difficult questions don't need to be answered. 

Of course if there are good answers to the questions, then even better!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,532940062
https://github.com/pydata/xarray/pull/3596#issuecomment-595506745,https://api.github.com/repos/pydata/xarray/issues/3596,595506745,MDEyOklzc3VlQ29tbWVudDU5NTUwNjc0NQ==,5635139,2020-03-06T00:04:03Z,2020-03-06T02:08:02Z,MEMBER,"> I do agree it can be confusing, but it is not unique in xarray. Dataset.shift only shifts `data_vars`, `bfill` and `ffill` only fill `data_vars`, etc.

I agree, I wouldn't have expected coords to be included given existing behavior. People can switch coords <> data_vars as needed, so there's an escape hatch

Edit: But it's more awkward for _indexes_ than non-index coords. The index becomes less useful with non-unique values, and generally indexes don't have nulls. I'm not sure what the other options would be: to some extent it's the intersection of `pad` with xarray's data model. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,532940062
https://github.com/pydata/xarray/pull/3596#issuecomment-595244925,https://api.github.com/repos/pydata/xarray/issues/3596,595244925,MDEyOklzc3VlQ29tbWVudDU5NTI0NDkyNQ==,5635139,2020-03-05T14:02:45Z,2020-03-05T14:02:45Z,MEMBER,"This looks excellent @mark-boer , thank you! 

I will try and have a proper look through today (but don't wait for me)","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,532940062