issue_comments: 258680571
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/1080#issuecomment-258680571 | https://api.github.com/repos/pydata/xarray/issues/1080 | 258680571 | MDEyOklzc3VlQ29tbWVudDI1ODY4MDU3MQ== | 1217238 | 2016-11-06T13:22:42Z | 2016-11-06T13:22:51Z | MEMBER |
Indeed. My thinking was the A stricter approach would have been to put everything under an attribute just for extensions, e.g.,
I'll add a note about the value of namespaces to the doc.
We could certainly turn this off (optionally) if there are cases where it does the wrong thing. Could you go into this in a little more detail, perhaps with a concrete example? My expectation was that this should have minimal design or performance downsides. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
187373423 |