issue_comments

Table actions

4 rows where author_association = "MEMBER", issue = 202124581 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 · 4 ✖

issue 1

  • New testing module and tests refactor · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
274439260 https://github.com/pydata/xarray/pull/1222#issuecomment-274439260 https://api.github.com/repos/pydata/xarray/issues/1222 MDEyOklzc3VlQ29tbWVudDI3NDQzOTI2MA== fmaussion 10050469 2017-01-23T09:34:43Z 2017-01-23T09:34:43Z MEMBER

My strongest preference is that all names have the same form, e.g., assert_X_equal, assert_X_identical and assert_X_allclose where X is the same token.

Agreed. Currently X is nothing, but I'm happy with either option you suggest. Also, my docstrings might need a short review as well to make sure I got them right. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New testing module and tests refactor 202124581
274328972 https://github.com/pydata/xarray/pull/1222#issuecomment-274328972 https://api.github.com/repos/pydata/xarray/issues/1222 MDEyOklzc3VlQ29tbWVudDI3NDMyODk3Mg== fmaussion 10050469 2017-01-22T12:49:00Z 2017-01-22T12:49:00Z MEMBER

I've implemented your comment and made an effort for better docstring. Let me know what you think.

As for the names, we currently have three new API-level functions. What about following names? - assert_data_equal (this makes it clear that we look at the data and not the attributes) - assert_identical (this makes it clear that the objects must be identical) - assert_allclose

I'm fine with assert_object_identical or assert_xarray_identical if you wish.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New testing module and tests refactor 202124581
274198593 https://github.com/pydata/xarray/pull/1222#issuecomment-274198593 https://api.github.com/repos/pydata/xarray/issues/1222 MDEyOklzc3VlQ29tbWVudDI3NDE5ODU5Mw== fmaussion 10050469 2017-01-20T22:37:01Z 2017-01-20T22:37:01Z MEMBER

done

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New testing module and tests refactor 202124581
274188191 https://github.com/pydata/xarray/pull/1222#issuecomment-274188191 https://api.github.com/repos/pydata/xarray/issues/1222 MDEyOklzc3VlQ29tbWVudDI3NDE4ODE5MQ== fmaussion 10050469 2017-01-20T21:45:50Z 2017-01-20T21:45:58Z MEMBER

I've implemented the changes you suggested, this is ready for another review.

I 've had problems locally with bottleneck (three tests didn't pass with bottleneck installed), but I haven't been able to reproduce this on travis so I guess it's just me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New testing module and tests refactor 202124581

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