issue_comments

Table actions

1 row where author_association = "NONE", issue = 584461380 and user = 13813076 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

  • mcdevitts · 1 ✖

issue 1

  • What should pad do about IndexVariables? · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
784502064 https://github.com/pydata/xarray/issues/3868#issuecomment-784502064 https://api.github.com/repos/pydata/xarray/issues/3868 MDEyOklzc3VlQ29tbWVudDc4NDUwMjA2NA== mcdevitts 13813076 2021-02-23T20:49:43Z 2021-02-23T20:49:43Z NONE

I'm not sure whether to open a separate feature request or just tag onto this one. Please correct me.

pad is an awesome method. I've used it to easily support interpolating or extrapolating dataarrays that happen to have unitary dimensions, or to quickly support a constant value extrapolation in any dimension. However, to do this, I have to go in and change alter the coords myself since the same value is just repeated.

Would it be possible to add an option that effectively adds "epsilon" to the newly added kwarg?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   What should pad do about IndexVariables? 584461380

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