id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
2266443797,PR_kwDOAMm_X85t4Nzs,8977,preliminary pr to examine the DataTree injected docs.,479480,open,0,,,5,2024-04-26T20:15:22Z,2024-04-26T22:36:00Z,,CONTRIBUTOR,,1,pydata/xarray/pulls/8977,"This PR should never be merged, it is opened only to run the build-the-docs with the changes from #8976 
 
I just wanted to make sure I could point to what the final doc pages will look like when datatree is released.

","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8977/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
2257054431,I_kwDOAMm_X86Gh-rf,8963,datatree ops.py migration cleanup,479480,open,0,,,0,2024-04-22T17:06:36Z,2024-04-22T18:23:31Z,,CONTRIBUTOR,,,,"### What is your issue?

During the 3/26/2024 design discussion meeting (#8747), we discussed the monkey patching of methods that was required to wrap datatree nodes with the desired Xarray API function.  This was a primarily done as a necessity due to the datatree code not living in the xarray repository. The better implementation could be to add the wrapping to xarray's `generate_aggregations.py` module.  The ultimate decision made by Stephan and Tom was to add this as a future issue (this one) and migrate the file as is for now. 







","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8963/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue
2187399013,I_kwDOAMm_X86CYQ9l,8836,DataTree should support Hashable names.,479480,open,0,,,0,2024-03-14T22:37:09Z,2024-03-15T04:57:44Z,,CONTRIBUTOR,,,,"### What is your issue?

In porting xarray-contrib/datatree into pydata/xarray. [We discovered some type mismatches](https://github.com/pydata/xarray/pull/8789#discussion_r1508388168). 

The general feeling was that we should support Hashable in order to improve `DataTree` interactions with `Dataset` and `DataArray`s.

The quick solution of changing the name type to Hashable in NamedNode fails quickly because of it's PathPurePath inheritance.

This issue just tracks that we want to come back to this.
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8836/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue
2167879988,I_kwDOAMm_X86BNzk0,8807,Collection of breaking changes in Datatree occurring during the migration from xarray-contrib/datatree into pydata/xarray proper,479480,open,0,,,3,2024-03-04T22:14:10Z,2024-03-04T22:57:49Z,,CONTRIBUTOR,,,,"### What is your issue?

This is an Issue to keep track of changes that have been made to DataTree from the initial migration ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8807/reactions"", ""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue