issues

Table actions

9 rows where comments = 1, repo = 197431109 and type = "issue" sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, author_association, created_at (date), updated_at (date), closed_at (date)

state 2

type 1

  • issue · 9 ✖

repo 1

  • dogsheep-beta · 9 ✖
id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
1817281557 I_kwDOC8SPRc5sUYQV 37 cannot use jinja filters in display? rprimet 10352819 closed 0     1 2023-07-23T20:09:54Z 2023-07-23T20:18:27Z 2023-07-23T20:18:26Z NONE  

Hi, I'm trying to have a display function in Dogsheep's config.yml that includes something like this:

```

{{ display.title }} (source)

{{ display.snippet|safe }}

```

Unfortunately, rendering fails with a message 'urls is undefined'.

The same happens if I'm trying to build a row URL manually, using filters like quote_plus (as my keys are URLs).

Any hints?

Thanks!

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/37/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
723861683 MDU6SXNzdWU3MjM4NjE2ODM= 28 Switch to using datasette.client simonw 9599 closed 0     1 2020-10-17T22:42:26Z 2020-10-17T23:00:47Z 2020-10-17T23:00:47Z MEMBER  

datasette.client is designed for this kind of thing, to replace this code: https://github.com/dogsheep/dogsheep-beta/blob/bed9df2b3ef68189e2e445427721a28f4e9b4887/dogsheep_beta/init.py#L223-L232

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/28/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
694136490 MDU6SXNzdWU2OTQxMzY0OTA= 15 Add a bunch of config examples simonw 9599 open 0     1 2020-09-05T17:58:43Z 2020-09-18T23:17:39Z   MEMBER  

I can bring these over from my personal Dogsheep.

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/15/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    
692386625 MDU6SXNzdWU2OTIzODY2MjU= 13 Support advanced FTS queries simonw 9599 closed 0     1 2020-09-03T21:29:56Z 2020-09-03T21:40:51Z 2020-09-03T21:40:51Z MEMBER  

simon willison NOT screenshot for example.

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/13/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
689847361 MDU6SXNzdWU2ODk4NDczNjE= 5 Add a context column that's not searchable simonw 9599 closed 0     1 2020-09-01T06:13:42Z 2020-09-03T18:43:50Z 2020-09-03T18:43:50Z MEMBER  

I sometimes like to configure titles that are things like "Comment on issue X" or "Photo in Golden Gate Park" - these shouldn't be included in the search index but should be stored so they can be displayed to provide context.

Add a column for this - probably called context - and make it so it can be populated.

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/5/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
691557547 MDU6SXNzdWU2OTE1NTc1NDc= 10 Category 3: received simonw 9599 closed 0     1 2020-09-03T01:40:36Z 2020-09-03T17:38:51Z 2020-09-03T17:38:51Z MEMBER  

A category for things that were sent to me: DMs, emails etc. Follows #7.

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/10/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
692125110 MDU6SXNzdWU2OTIxMjUxMTA= 11 Public / Private mechanism simonw 9599 closed 0     1 2020-09-03T16:47:03Z 2020-09-03T17:33:52Z 2020-09-03T17:33:52Z MEMBER  

Some of the data in Dogsheep is stuff that was written publicly - tweets, blog posts, GitHub commits to public repos.

Some of it is private data - emails, photos, direct messages, Swarm checkins, commits to private repos.

Being able to filter for just one or the other (or both) would be useful. Especially when giving demos!

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/11/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
691369691 MDU6SXNzdWU2OTEzNjk2OTE= 8 Create a view for running faceted searches simonw 9599 closed 0     1 2020-09-02T19:44:07Z 2020-09-02T19:50:47Z 2020-09-02T19:50:47Z MEMBER  

sql select search_index_fts.rank, search_index.rowid, search_index.[table], search_index.key, search_index.title, search_index.timestamp, search_index.search_1 from search_index join search_index_fts on search_index.rowid = search_index_fts.rowid order by search_index_fts.rank, search_index.timestamp desc

 dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/8/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
689839399 MDU6SXNzdWU2ODk4MzkzOTk= 4 Optimize the FTS table simonw 9599 closed 0     1 2020-09-01T05:58:17Z 2020-09-01T06:10:08Z 2020-09-01T06:10:08Z MEMBER  
dogsheep-beta 197431109 issue     
{
    "url": "https://api.github.com/repos/dogsheep/dogsheep-beta/issues/4/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);