sha,message,author_date,committer_date,raw_author,raw_committer,repo,author,committer
2e2825869fc2655b5fcadc743f6f9dec7a49bc65,"Test for --get --actor, refs #2153",2023-08-28T20:18:24Z,2023-08-28T20:18:24Z,13ae486343ea6454a93114c6f558ffea2f2c6874,13ae486343ea6454a93114c6f558ffea2f2c6874,107914493,9599,9599
d8351b08edb08484f5505f509c6101c56a8bba4a,"datasette --get --actor 'JSON' option, closes #2153

Refs #2154",2023-08-28T20:14:48Z,2023-08-28T20:15:38Z,13ae486343ea6454a93114c6f558ffea2f2c6874,13ae486343ea6454a93114c6f558ffea2f2c6874,107914493,9599,9599
d9aad1fd042a25d226f2ace1f7827b4602761038,"-s/--setting x y gets merged into datasette.yml, refs #2143, #2156

This change updates the `-s/--setting` option to `datasette serve` to allow it to be used to set arbitrarily complex nested settings in a way that is compatible with the new `-c datasette.yml` work happening in:
- #2143

It will enable things like this:
```
datasette data.db --setting plugins.datasette-ripgrep.path ""/home/simon/code""
```
For the moment though it just affects [settings](https://docs.datasette.io/en/1.0a4/settings.html) - so you can do this:
```
datasette data.db --setting settings.sql_time_limit_ms 3500
```
I've also implemented a backwards compatibility mechanism, so if you use it this way (the old way):
```
datasette data.db --setting sql_time_limit_ms 3500
```
It will notice that the setting you passed is one of Datasette's core settings, and will treat that as if you said `settings.sql_time_limit_ms` instead.",2023-08-28T20:06:14Z,2023-08-28T20:06:14Z,13ae486343ea6454a93114c6f558ffea2f2c6874,cd792325681cbad9f663f2879d8b69f1edbb678f,107914493,9599,19864447