issue_comments: 752714747

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/987#issuecomment-752714747 https://api.github.com/repos/simonw/datasette/issues/987 752714747 MDEyOklzc3VlQ29tbWVudDc1MjcxNDc0Nw== 9599 2020-12-30T18:23:08Z 2020-12-30T18:23:20Z OWNER

In terms of "places to put your plugin content", the simplest solution I can think of is something like this: ```html

``` Alternative designs:

  • A documented JavaScript function that returns the CSS selector where plugins should put their content
  • A documented JavaScript function that returns a DOM node where plugins should put their content. This would allow the JavaScript to create the element if it does not already exist (though it wouldn't be obvious WHERE that element should be created)
  • Documented JavaScript functions for things like "append this node/HTML to the place-where-plugins-go"

I think the original option - an empty <div> with a known id attribute - is the right one to go with here. It's the simplest, it's very easy for custom template authors to understand and it acknowledges that plugins may have all kinds of extra crazy stuff they want to do - like checking in that div to see if another plugin has written to it already, for example.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 712984738