issue_comments
1 row where issue = 341643235 and user = 25172489 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support non-string dimension/variable names · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
979759002 | https://github.com/pydata/xarray/issues/2292#issuecomment-979759002 | https://api.github.com/repos/pydata/xarray/issues/2292 | IC_kwDOAMm_X846Ze-a | derhintze 25172489 | 2021-11-26T07:48:21Z | 2021-11-26T07:52:42Z | NONE | Would like to chime in that we use a similar approach as in the last comment of @DerWeh . But we extend this by overloading the ``` class Dimension(str, enum.Enum): """Base class for all dimension enums
``` Using this the xarray output is more consistent: ```
We then have deserialization code, that re-creates enum members when reading NetCDF files with corresponding dimensions (and coordinates). Access to coordinates works with enum members as well as their string value. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support non-string dimension/variable names 341643235 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1