issue_comments

Table actions

1 row where issue = 1385143758 and user = 22566757 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

  • DWesl · 1 ✖

issue 1

  • Fix `utils.get_axis` with kwargs · 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
1259913775 https://github.com/pydata/xarray/pull/7080#issuecomment-1259913775 https://api.github.com/repos/pydata/xarray/issues/7080 IC_kwDOAMm_X85LGMIv DWesl 22566757 2022-09-27T18:47:00Z 2022-09-27T18:47:00Z CONTRIBUTOR

I think the current default for two-dimensional plots is to try to re-use an existing axis if neither row nor col are set (implied by documentation for ax argument in the description of the DataArray.plot descriptor). Would this PR change that behavior, and should that be documented?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix `utils.get_axis` with kwargs 1385143758

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