issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 525972395 and user = 5635139 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

  • max-sixty · 3 ✖

issue 1

  • Fix documentation · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
556897541 https://github.com/pydata/xarray/pull/3554#issuecomment-556897541 https://api.github.com/repos/pydata/xarray/issues/3554 MDEyOklzc3VlQ29tbWVudDU1Njg5NzU0MQ== max-sixty 5635139 2019-11-21T03:12:28Z 2019-11-21T03:12:28Z MEMBER

I'd like to have documentation available for anything in the public API, so that it can be a useful reference for both previously existing and new code. I think for deprecated functionality it makes the most sense to keep the docs, but warn prominently that it should not be used in new code (e.g. https://unidata.github.io/MetPy/dev/api/generated/metpy.calc.html#deprecated)?

I think this is a pretty good balance, i.e. a section with Deprecated / Pending Deprecation. If we can do that as part of this then great; otherwise I'm happy to have a go

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix documentation 525972395
556331512 https://github.com/pydata/xarray/pull/3554#issuecomment-556331512 https://api.github.com/repos/pydata/xarray/issues/3554 MDEyOklzc3VlQ29tbWVudDU1NjMzMTUxMg== max-sixty 5635139 2019-11-20T20:09:56Z 2019-11-20T20:09:56Z MEMBER

the docs fail because it cannot find a rasterio / tif file.

Hmmm, I haven't seen that before. Do you know whether it fails on master? (I can check too)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix documentation 525972395
556322791 https://github.com/pydata/xarray/pull/3554#issuecomment-556322791 https://api.github.com/repos/pydata/xarray/issues/3554 MDEyOklzc3VlQ29tbWVudDU1NjMyMjc5MQ== max-sixty 5635139 2019-11-20T20:02:37Z 2019-11-20T20:02:37Z MEMBER

My thought behind removing drop was to only list methods that we recommend people use. We're keeping drop for back-compat reasons, but I wouldn't recommend anyone who is creating new code use it.

But maybe that's too aggressive. Any thoughts anyone?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix documentation 525972395

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