issue_comments

Table actions

3 rows where issue = 38848839 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • shoyer · 3 ✖

issue 1

  • Consistent use of abbreviations: attrs, dims, coords · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
52151665 https://github.com/pydata/xarray/issues/190#issuecomment-52151665 https://api.github.com/repos/pydata/xarray/issues/190 MDEyOklzc3VlQ29tbWVudDUyMTUxNjY1 shoyer 1217238 2014-08-14T07:24:29Z 2014-08-14T07:24:29Z MEMBER

Actually, I am going to go ahead and rename noncoordinates to noncoords. Deprecating/removing that property will have to wait.

Otherwise everything was done in #194.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Consistent use of abbreviations: attrs, dims, coords 38848839
52012201 https://github.com/pydata/xarray/issues/190#issuecomment-52012201 https://api.github.com/repos/pydata/xarray/issues/190 MDEyOklzc3VlQ29tbWVudDUyMDEyMjAx shoyer 1217238 2014-08-13T05:48:28Z 2014-08-13T07:48:59Z MEMBER

I've decided that we do want to switch to using coords and dims.

I have not renamed noncoordinates to noncoords. I'm going to deprecate that property instead (#211).

Also I haven't renamed xray.Coordinate yet -- that will probably become xray.CoordIndex eventually (#197) but for now is OK.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Consistent use of abbreviations: attrs, dims, coords 38848839
50713976 https://github.com/pydata/xarray/issues/190#issuecomment-50713976 https://api.github.com/repos/pydata/xarray/issues/190 MDEyOklzc3VlQ29tbWVudDUwNzEzOTc2 shoyer 1217238 2014-07-31T05:26:39Z 2014-07-31T05:26:39Z MEMBER

There is at least one major advantage to using abbreviations: less typing and shorter lines of code!

e.g., compare:

python x = xray.Coord('x', np.arange(10)) y = xray.Coord('y', ['a', 'b', 'c']) arr = xray.DataArray(data, dims=['x', 'y'], coords=[x, y]) 'x' in arr.dims

and

python x = xray.Coordinate('x', np.arange(10)) y = xray.Coordinate('y', ['a', 'b', 'c']) arr = xray.DataArray(data, dimensions=['x', 'y'], coordinates=[x, y]) 'x' in arr.dimensions

h5py does use dims instead of dimensions: http://docs.h5py.org/en/2.3/high/dims.html and Iris also uses the abbreviations "dim" and "coord".

These are pretty common/obvious abbreviations and they are fundamental enough that I would not worry about imposing them on our users.

Right now, I am leaning toward switching to always using dim/dims and coord/coords/Coord before the 0.2 release. But I don't want to be too hasty about this -- any opinions out there? The counter argument would be that I should stop wasting my time bike-shedding (especially after I've already released this stuff out in the wild).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Consistent use of abbreviations: attrs, dims, coords 38848839

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