issue_comments: 497194179
This data as json
| 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/495#issuecomment-497194179 | https://api.github.com/repos/simonw/datasette/issues/495 | 497194179 | MDEyOklzc3VlQ29tbWVudDQ5NzE5NDE3OQ== | 9599 | 2019-05-30T04:04:01Z | 2019-05-30T04:04:01Z | OWNER | I think there are a few steps to solving this: * Define a variant of `?_facet_m2m={..}` that takes a JSON object which specifies which middle and destination table should be used, and via which columns * Teach the Facet `ManyToManyFacet.suggest()` method to check for multiple conflicting m2m relationships and use the new JSON URL for them. Also pick non-conflicting display names for those facets. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 450032134 |