issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 293345254 and user = 6815844 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

  • fujiisoup · 1 ✖

issue 1

  • roll doesn't handle periodic boundary conditions well · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
362104114 https://github.com/pydata/xarray/issues/1875#issuecomment-362104114 https://api.github.com/repos/pydata/xarray/issues/1875 MDEyOklzc3VlQ29tbWVudDM2MjEwNDExNA== fujiisoup 6815844 2018-01-31T23:19:27Z 2018-01-31T23:19:27Z MEMBER

I like the option 1. I agree that the circular coordinate is used in many physics fields (actually I'm not from geoscience and I also sometimes use the circular coordinate), but one confusing sene I can think of is when using it in radian, (0, 0.5 pi, pi ...). Manual overwite would be more explicit

Another option could be to add a circular cooredinate class after #1603 is implemented?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   roll doesn't handle periodic boundary conditions well 293345254

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