{"html_url": "https://github.com/simonw/datasette/issues/1143#issuecomment-1038289584", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1143", "id": 1038289584, "node_id": "IC_kwDOBm6k_c494wqw", "user": {"value": 9599, "label": "simonw"}, "created_at": "2022-02-13T17:40:50Z", "updated_at": "2022-02-13T17:41:17Z", "author_association": "OWNER", "body": "The way Drupal does this is interesting; https://www.drupal.org/node/2715637 - it supports the following YAML:\r\n```yaml\r\n  # Configure Cross-Site HTTP requests (CORS).\r\n  # Read https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS\r\n  # for more information about the topic in general.\r\n  # Note: By default the configuration is disabled.\r\n cors.config:\r\n   enabled: false\r\n   # Specify allowed headers, like 'x-allowed-header'.\r\n   allowedHeaders: []\r\n   # Specify allowed request methods, specify ['*'] to allow all possible ones.\r\n   allowedMethods: []\r\n   # Configure requests allowed from specific origins.\r\n   allowedOrigins: ['*']\r\n   # Sets the Access-Control-Expose-Headers header.\r\n   exposedHeaders: false\r\n   # Sets the Access-Control-Max-Age header.\r\n   maxAge: false\r\n   # Sets the Access-Control-Allow-Credentials header.\r\n   supportsCredentials: false\r\n```", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 764059235, "label": "More flexible CORS support in core, to encourage good security practices"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/sqlite-utils/issues/398#issuecomment-1038336591", "issue_url": "https://api.github.com/repos/simonw/sqlite-utils/issues/398", "id": 1038336591, "node_id": "IC_kwDOCGYnMM4948JP", "user": {"value": 25778, "label": "eyeseast"}, "created_at": "2022-02-13T18:48:21Z", "updated_at": "2022-02-13T18:49:49Z", "author_association": "CONTRIBUTOR", "body": "Been chipping away at this between other things and realized `sqlite-utils init-spatialite` is probably unnecessary. Any of the other commands requires running `db.init_spatialite` to have the extension functions available, and that will do everything `init-spatialite` would do.\r\n\r\nI think it's probably worth keeping a SpatiaLite flag on `create-database` in case you wanted to create all the spatial metadata up front. Otherwise, it's going to get added the first time you run `add-geometry-column` or `create-spatial-index`, which is probably fine in most cases.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1124237013, "label": "Add SpatiaLite helpers to CLI"}, "performed_via_github_app": null}