github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/702#issuecomment-603631746 | https://api.github.com/repos/simonw/datasette/issues/702 | 603631746 | MDEyOklzc3VlQ29tbWVudDYwMzYzMTc0Ng== | 9599 | 2020-03-25T04:19:36Z | 2020-03-25T04:19:36Z | OWNER | Shipped in 0.39: https://datasette.readthedocs.io/en/latest/changelog.html#v0-39 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
585390482 | |
https://github.com/simonw/datasette/issues/702#issuecomment-602139031 | https://api.github.com/repos/simonw/datasette/issues/702 | 602139031 | MDEyOklzc3VlQ29tbWVudDYwMjEzOTAzMQ== | 9599 | 2020-03-22T02:36:09Z | 2020-03-22T02:36:09Z | OWNER | Found a bug: if you click on a column with a default sort order applied to it you get: "Cannot use _sort and _sort_desc at the same time" | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
585390482 | |
https://github.com/simonw/datasette/issues/702#issuecomment-602138528 | https://api.github.com/repos/simonw/datasette/issues/702 | 602138528 | MDEyOklzc3VlQ29tbWVudDYwMjEzODUyOA== | 9599 | 2020-03-22T02:29:23Z | 2020-03-22T02:29:23Z | OWNER | Documentation: https://datasette.readthedocs.io/en/latest/metadata.html#setting-a-default-sort-order | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
585390482 | |
https://github.com/simonw/datasette/issues/702#issuecomment-602122492 | https://api.github.com/repos/simonw/datasette/issues/702 | 602122492 | MDEyOklzc3VlQ29tbWVudDYwMjEyMjQ5Mg== | 9599 | 2020-03-22T00:01:56Z | 2020-03-22T00:01:56Z | OWNER | I'm going to mirror the URL syntax here, so the options in `metadata.json` will be: * `"sort": "created"` to default sort by created * `"sort_desc": "created"` to default sort by created descending It will throw an error if you try to define both. If I add the ability to sort by multiple columns in the future (#197) I can allow a list of columns here - though I'm not sure how I would represent "sort by created asc, title desc" in that case. If you want to disable user-specified sorting you can do so using the existing `"sortable_columns": []` mechanism. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
585390482 | |
https://github.com/simonw/datasette/issues/702#issuecomment-601963535 | https://api.github.com/repos/simonw/datasette/issues/702 | 601963535 | MDEyOklzc3VlQ29tbWVudDYwMTk2MzUzNQ== | 9599 | 2020-03-21T00:20:50Z | 2020-03-21T00:20:50Z | OWNER | I can solve #677 (The first time you click sort by ID it should show you results in reverse order) at the same time. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
585390482 |