issue_comments
4 rows where issue = 414552031 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Documentation on accessors? · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 472446172 | https://github.com/pydata/xarray/issues/2788#issuecomment-472446172 | https://api.github.com/repos/pydata/xarray/issues/2788 | MDEyOklzc3VlQ29tbWVudDQ3MjQ0NjE3Mg== | dcherian 2448579 | 2019-03-13T14:31:18Z | 2019-03-13T14:31:18Z | MEMBER | http://xarray.pydata.org/en/stable/internals.html#extending-xarray
There seems to be a misunderstanding. The docs say that defining an accessor is equivalent to defining an additional property of the What about that example isn't clear enough? Would it help if the example in @TomNicholas's comment above was added to the documentation? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation on accessors? 414552031 | |
| 472441105 | https://github.com/pydata/xarray/issues/2788#issuecomment-472441105 | https://api.github.com/repos/pydata/xarray/issues/2788 | MDEyOklzc3VlQ29tbWVudDQ3MjQ0MTEwNQ== | achapkowski 5131271 | 2019-03-13T14:19:31Z | 2019-03-13T14:19:31Z | NONE | @dcherian A non-trivial example would help for both types of accessor patterns would help a lot and the best practice defined by the dev team on how to extend the API when needed. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation on accessors? 414552031 | |
| 472433698 | https://github.com/pydata/xarray/issues/2788#issuecomment-472433698 | https://api.github.com/repos/pydata/xarray/issues/2788 | MDEyOklzc3VlQ29tbWVudDQ3MjQzMzY5OA== | dcherian 2448579 | 2019-03-13T14:01:03Z | 2019-03-13T14:01:03Z | MEMBER | @achapkowski We would appreciate it if you could suggest changes that would make the documentation less confusing. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation on accessors? 414552031 | |
| 467490757 | https://github.com/pydata/xarray/issues/2788#issuecomment-467490757 | https://api.github.com/repos/pydata/xarray/issues/2788 | MDEyOklzc3VlQ29tbWVudDQ2NzQ5MDc1Nw== | TomNicholas 35968931 | 2019-02-26T15:46:06Z | 2019-02-26T15:46:06Z | MEMBER |
You don't really need to implement anything, you're effectively just adding new methods and properties to the class, you don't need to reimplement anything which is already there. ```python @xarray.register_dataset_accessor('example') class ExampleDataArrayAccessor(): def init(self, da): pass
ds = xr.Dataset({'longitude': np.linspace(0, 10), 'latitude': np.linspace(0, 20)})
ds.example.hello_world()
You've linked to the only example current in the official documentation. (I think there should be more examples.) However I found reading the discussion and examples in this issue thread pretty helpful. Also I have a very simple example of creating a dataset accessor here. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Documentation on accessors? 414552031 |
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