issue_comments
5 rows where author_association = "MEMBER" and issue = 327725925 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- HoloViews based plotting API · 5 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 393764489 | https://github.com/pydata/xarray/issues/2199#issuecomment-393764489 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5Mzc2NDQ4OQ== | shoyer 1217238 | 2018-06-01T05:36:11Z | 2018-06-01T05:36:11Z | MEMBER | I'm not strongly opposed to something like
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
HoloViews based plotting API 327725925 | |
| 393292090 | https://github.com/pydata/xarray/issues/2199#issuecomment-393292090 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzI5MjA5MA== | rabernat 1197350 | 2018-05-30T19:42:43Z | 2018-05-30T19:42:43Z | MEMBER | Oh and another big 👍 to the datashader integration. This is crucial for my datasets. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
HoloViews based plotting API 327725925 | |
| 393291809 | https://github.com/pydata/xarray/issues/2199#issuecomment-393291809 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzI5MTgwOQ== | rabernat 1197350 | 2018-05-30T19:41:56Z | 2018-05-30T19:41:56Z | MEMBER | I am a big fan of holoviews and have been using it extensively for my own work in recent months. So obviously I am a big 👍 on this integration. I agree the accessor is the best option for now, but I have no strong opinions about the name of the accessor. Some features I would like to see are things that go beyond the plotting capabilities associated with the matplotlib engine. For example:
|
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
HoloViews based plotting API 327725925 | |
| 393214964 | https://github.com/pydata/xarray/issues/2199#issuecomment-393214964 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzIxNDk2NA== | shoyer 1217238 | 2018-05-30T15:53:06Z | 2018-05-30T15:53:06Z | MEMBER | Very cool! I also think this would be a good use case for a new accessor, perhaps An |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
HoloViews based plotting API 327725925 | |
| 393164716 | https://github.com/pydata/xarray/issues/2199#issuecomment-393164716 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzE2NDcxNg== | fmaussion 10050469 | 2018-05-30T13:37:41Z | 2018-05-30T13:37:41Z | MEMBER | It looks like a good use case for accessors. The syntax could then be: |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
HoloViews based plotting API 327725925 |
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 3