issue_comments

Table actions

2 rows where issue = 1642635191 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Add reset_encoding to Dataset and DataArray objects · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1485989169 https://github.com/pydata/xarray/issues/7686#issuecomment-1485989169 https://api.github.com/repos/pydata/xarray/issues/7686 IC_kwDOAMm_X85YkmUx jhamman 2443309 2023-03-27T23:21:27Z 2023-03-27T23:21:27Z MEMBER

As I said in #4817, I think we should pursue the keep_encoding option (in addition to the proposal in this PR).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add reset_encoding to Dataset and DataArray objects 1642635191
1485752281 https://github.com/pydata/xarray/issues/7686#issuecomment-1485752281 https://api.github.com/repos/pydata/xarray/issues/7686 IC_kwDOAMm_X85YjsfZ keewis 14808389 2023-03-27T19:33:59Z 2023-03-27T19:36:46Z MEMBER

see also #6323 and #4817

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   Add reset_encoding to Dataset and DataArray objects 1642635191

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