issue_comments

Table actions

1 row where issue = 1316549018 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • keewis · 1 ✖

issue 1

  • Rely on array backend for string formatting · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1203860057 https://github.com/pydata/xarray/pull/6823#issuecomment-1203860057 https://api.github.com/repos/pydata/xarray/issues/6823 IC_kwDOAMm_X85HwXJZ keewis 14808389 2022-08-03T12:03:44Z 2022-08-08T12:32:21Z MEMBER

But it won't feel very consistent once string formatting are used though.

I guess we could introduce some sort of xarray specific formatting mini-language to solve that? For example: - f"{arr:r}": print the object's repr (the default) - f"{arr:b}": print the array backend's repr (only for DataArray / Variable)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Rely on array backend for string formatting 1316549018

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