issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 170305429 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

issue 1

  • BUG: Repr on inherited classes is incorrect · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
238755783 https://github.com/pydata/xarray/issues/957#issuecomment-238755783 https://api.github.com/repos/pydata/xarray/issues/957 MDEyOklzc3VlQ29tbWVudDIzODc1NTc4Mw== max-sixty 5635139 2016-08-10T03:22:07Z 2016-08-10T03:22:07Z MEMBER

I would be interested to know if registering an accessor works

Yes I knew about that. Our use case is a bit different - rather than add a property to all Datasets is the environment, we want to do it to specific classes. We used to have a class that had an underlying Dataset (or many DataFrames) and then offered accessor properties on top. So the current solution is a bit nicer, in that it integrates those two objects (the custom class and the underlying Dataset) into one Numerical operations probably aren't reliable, but that's OK for us

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   BUG: Repr on inherited classes is incorrect 170305429
238745229 https://github.com/pydata/xarray/issues/957#issuecomment-238745229 https://api.github.com/repos/pydata/xarray/issues/957 MDEyOklzc3VlQ29tbWVudDIzODc0NTIyOQ== shoyer 1217238 2016-08-10T01:56:22Z 2016-08-10T01:56:22Z MEMBER

I would be interested to know if registering an accessor works for you, which was designed for exactly this sort of use case: http://xarray.pydata.org/en/stable/internals.html#extending-xarray

The reason why I chose not to just use the qualified name is that xarray.core.dataset.Dataset is a little long, and also points users in the direction of private API.

But I'd be happy to use qualified names for subclasses not builtin to xarray. Currently you can find this logic in dataset_repr and array_repr at the bottom of core/formatting.py. You'd just need to write a helper function to calculate the class name rather than our current use of u'<xarray.%s>' % type(ds).__name__. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   BUG: Repr on inherited classes is incorrect 170305429

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