issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 469440752 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
512582286 https://github.com/pydata/xarray/issues/3139#issuecomment-512582286 https://api.github.com/repos/pydata/xarray/issues/3139 MDEyOklzc3VlQ29tbWVudDUxMjU4MjI4Ng== max-sixty 5635139 2019-07-17T21:50:29Z 2019-07-17T21:50:29Z MEMBER

I'm +1 on the relative dim / coord importance

But I also think this would be v disruptive, even with a deprecation period and some clever guessing. Maybe I'm being overly precious (we successfully changed the name of the library!); but I can imagine hundreds of warnings for people to swap argument order all over their code.

A couple of ideas if we did decide this: - Encourage people to pass dim and coords as keyword rather than positional args - Read them as *args prior to a ** separator and then warn if passed there - Then at least there's no ambiguity - An even later version could remove this restriction and reverse the order - Is there any from_foo constructors that would help here? I don't think so, but I've often found that resolves constructor discussions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Change the signature of DataArray to DataArray(data, dims, coords, ...)? 469440752

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]);