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/issues/3361#issuecomment-537669216,https://api.github.com/repos/pydata/xarray/issues/3361,537669216,MDEyOklzc3VlQ29tbWVudDUzNzY2OTIxNg==,1956032,2019-10-02T20:35:26Z,2019-10-02T20:35:26Z,CONTRIBUTOR,"Thanks for the example @jthielen, this looks great !

May be it would be better to not show to readers the accessor class name, since it will never be seen on the API frontend, only the scope name will.  

So it would be great to be able to have the documentation to read something like:  

`xarray.DataSet.<scope_name>.<accessor_method_or_property>`  

instead of:  

`<package_name>.xarray.<accessor_class_name>.<accessor_method_or_property>`
(in the case where the accessor class is in xarray.py file on the package)

But I don't know how to manage that with sphinx documentation
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,500949040
https://github.com/pydata/xarray/issues/3361#issuecomment-537564221,https://api.github.com/repos/pydata/xarray/issues/3361,537564221,MDEyOklzc3VlQ29tbWVudDUzNzU2NDIyMQ==,3460034,2019-10-02T16:05:57Z,2019-10-02T16:05:57Z,CONTRIBUTOR,"@gmaze Just as an example, here is what we recently added for MetPy: https://unidata.github.io/MetPy/latest/api/generated/metpy.xarray.html. Previously, we just had a narrative-form tutorial.

If there are other recommendations, it would be great to incorporate those into MetPy as well!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,500949040