issue_comments

Table actions

1 row where issue = 320632674 and user = 10050469 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

  • fmaussion · 1 ✖

issue 1

  • ENH: added FacetGrid functionality to line plots · 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
388637796 https://github.com/pydata/xarray/pull/2107#issuecomment-388637796 https://api.github.com/repos/pydata/xarray/issues/2107 MDEyOklzc3VlQ29tbWVudDM4ODYzNzc5Ng== fmaussion 10050469 2018-05-13T16:09:45Z 2018-05-13T16:09:45Z MEMBER

writing new functions that will verify that stuff works as it should

Yes. See here for example tests for FacetGrid. Testing plotting functions is not trivial but we usually test only very basic functionality. You might find some examples in here.

or that the new addition does not mess up previous plotting behavior?

This is usually covered by continuous integration, which already ran the tests on your current PR (the "all checks have passed" green button above). So on this side you are safe for now, unless our previous tests weren't efficient enough ;-)

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: added FacetGrid functionality to line plots 320632674

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