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/2690#issuecomment-456039039,https://api.github.com/repos/pydata/xarray/issues/2690,456039039,MDEyOklzc3VlQ29tbWVudDQ1NjAzOTAzOQ==,35968931,2019-01-21T11:17:56Z,2019-01-21T11:17:56Z,MEMBER,"> Why not just encourage users to copy/paste the helper function into their own codebases?

Just because they aren't going to know it exists unless we put it in a public place I suppose?

Happy to do any of those things, I just think that having some kind of public function/copyable code example etc is a simple thing for us to do that will make it just a bit easier for users who want to build upon xarray.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,400678645
https://github.com/pydata/xarray/pull/2690#issuecomment-455600050,https://api.github.com/repos/pydata/xarray/issues/2690,455600050,MDEyOklzc3VlQ29tbWVudDQ1NTYwMDA1MA==,35968931,2019-01-18T16:12:25Z,2019-01-18T16:12:25Z,MEMBER,"> it would mean effectively freezing the output of this helper function

Or we could have a public `create_example_data`, and an internal `create_test_data`? That way to begin with `create_example_data` is just an alias to the internal `create_test_data`, but if we end up needing to change the internal one (to test for some new type of common indexing edge case for example) then we can just separate them?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,400678645