issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 213426608 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

These facets timed out: author_association, issue

user 1

  • shoyer · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
457881189 https://github.com/pydata/xarray/issues/1306#issuecomment-457881189 https://api.github.com/repos/pydata/xarray/issues/1306 MDEyOklzc3VlQ29tbWVudDQ1Nzg4MTE4OQ== shoyer 1217238 2019-01-27T01:36:35Z 2019-01-27T01:37:53Z MEMBER

Closing this. We use "xarray" in the middle of sentences and "Xarray" at the start but aren't that strict about it.

Yes: Xarray (at start of sentences), xarray (in middle) No: XArray, xArray

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray vs Xarray vs XArray 213426608
358195876 https://github.com/pydata/xarray/issues/1306#issuecomment-358195876 https://api.github.com/repos/pydata/xarray/issues/1306 MDEyOklzc3VlQ29tbWVudDM1ODE5NTg3Ng== shoyer 1217238 2018-01-17T04:46:17Z 2018-01-17T04:46:17Z MEMBER

I like xarray because it is the same as the python package. However, for aesthetic reasons I capitalize Xarray when used for titles or at the beginning of a sentence...

I agree. This is the capitalization convention used by netCDF.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray vs Xarray vs XArray 213426608
292835259 https://github.com/pydata/xarray/issues/1306#issuecomment-292835259 https://api.github.com/repos/pydata/xarray/issues/1306 MDEyOklzc3VlQ29tbWVudDI5MjgzNTI1OQ== shoyer 1217238 2017-04-10T02:30:00Z 2017-04-10T02:30:00Z MEMBER

Are/have there beein any thoughts or discussions on whether xa would be more fitting?

Let's not open that can of worms :). I actually usually import the package as xarray these days, since I like the explicitness, and due to xarray's extensive methods it's rare to need to use many functions on one line (as one does for numpy).

I am also weekly in favor of "Xarray" for the proper name, if only to avoid "XArray". But I don't know if I care enough to update all the docs.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray vs Xarray vs XArray 213426608

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);