home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER" and issue = 216329175 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

  • shoyer 2
  • fmaussion 1

issue 1

  • Truncate long lines in repr of Dataset.attrs · 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
288830638 https://github.com/pydata/xarray/issues/1319#issuecomment-288830638 https://api.github.com/repos/pydata/xarray/issues/1319 MDEyOklzc3VlQ29tbWVudDI4ODgzMDYzOA== shoyer 1217238 2017-03-23T19:14:01Z 2017-03-23T19:14:01Z MEMBER

Sounds like there is support here.

@Zac-HD Any interest in putting together a pull request? See here for the existing logic: https://github.com/pydata/xarray/blob/b3fc6c4e4fafdf4f075b791594633970a787ad79/xarray/core/formatting.py#L255

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Truncate long lines in repr of Dataset.attrs 216329175
288829627 https://github.com/pydata/xarray/issues/1319#issuecomment-288829627 https://api.github.com/repos/pydata/xarray/issues/1319 MDEyOklzc3VlQ29tbWVudDI4ODgyOTYyNw== fmaussion 10050469 2017-03-23T19:10:18Z 2017-03-23T19:10:18Z MEMBER

I am in favor of truncating the attrs too.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Truncate long lines in repr of Dataset.attrs 216329175
288827576 https://github.com/pydata/xarray/issues/1319#issuecomment-288827576 https://api.github.com/repos/pydata/xarray/issues/1319 MDEyOklzc3VlQ29tbWVudDI4ODgyNzU3Ng== shoyer 1217238 2017-03-23T19:02:39Z 2017-03-23T19:02:39Z MEMBER

OK, I'm not opposed to this. Truncating at 500 characters was basically a minimal sanity check -- we could certainly go further than this.

Anyone else have opinions here about sane default behavior? I don't work with files with lots of long attributes.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Truncate long lines in repr of Dataset.attrs 216329175

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]);
Powered by Datasette · Queries took 52.021ms · About: xarray-datasette