issue_comments

Table actions

3 rows where issue = 558977158 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1194287221 https://github.com/pydata/xarray/issues/3743#issuecomment-1194287221 https://api.github.com/repos/pydata/xarray/issues/3743 IC_kwDOAMm_X85HL2B1 arsenovic 1228240 2022-07-25T16:02:27Z 2022-07-25T17:22:41Z NONE

would be nice better to wrap it and make it round trippable (especially for simple things like None ) 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` 558977158
769072560 https://github.com/pydata/xarray/issues/3743#issuecomment-769072560 https://api.github.com/repos/pydata/xarray/issues/3743 MDEyOklzc3VlQ29tbWVudDc2OTA3MjU2MA== Shaunakde 2545129 2021-01-28T14:00:34Z 2021-01-28T14:00:34Z NONE

This would be a handy feature. Especially for writing unit tests, where often it's okay if the attributes aren't reserialized exactly. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` 558977158
595401671 https://github.com/pydata/xarray/issues/3743#issuecomment-595401671 https://api.github.com/repos/pydata/xarray/issues/3743 MDEyOklzc3VlQ29tbWVudDU5NTQwMTY3MQ== max-sixty 5635139 2020-03-05T19:22:07Z 2020-03-05T19:22:07Z MEMBER

Thanks for the suggestion. One issue here is that it's not round-trippable; i.e. it wouldn't get deserialized into an object on being loaded.

To the extent people don't think that's an issue, we could take a PR. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A suggested solution to the `TypeError: Invalid value for attr:` error upon `.to_netcdf` 558977158

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