issue_comments

Table actions

1 row where issue = 786093946 and user = 5821660 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

  • kmuehlbauer · 1 ✖

issue 1

  • add new backend api documentation · 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
789977144 https://github.com/pydata/xarray/pull/4810#issuecomment-789977144 https://api.github.com/repos/pydata/xarray/issues/4810 MDEyOklzc3VlQ29tbWVudDc4OTk3NzE0NA== kmuehlbauer 5821660 2021-03-03T18:58:03Z 2021-03-03T18:58:03Z MEMBER

@jhamman As I'm currently implementing xarray backends for reading weather radar data, I've already closely followed the adventures of @aurghs and @alexamici.

To the current state of the backend documentation I can say that it is very well written and understandable (also for non native speakers) and I could easily follow the train of thought.

From my perspective: I would not try to show extensive examples in the beginning, but would extend/rearrange documentation after first users issued problems/asked questions. So that only things get special documentation which are not immediately clear from users perspective.

This is a really remarkable extension which will boost usage of xarray. Thanks! 

{
    "total_count": 3,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 2,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   add new backend api documentation 786093946

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