* Show comma-separated city, state and country in infobox and in gallery mode. All of the values that are non-empty will be shown.
* methodcall to isPhoto
* Unit test and bugfix for CreationDate (#8)
* fixed the DiskManagerWorker test
* s (#10)
* Unit test and bugfix for CreationDate (#8)
* fixed the DiskManagerWorker test
---------
Co-authored-by: Patrik J. Braun <bpatrik@users.noreply.github.com>
* s (#11)
* Unit test and bugfix for CreationDate (#8)
* fixed the DiskManagerWorker test
---------
Co-authored-by: Patrik J. Braun <bpatrik@users.noreply.github.com>
* 9ij (#12)
* Unit test and bugfix for CreationDate (#8)
* fixed the DiskManagerWorker test
---------
Co-authored-by: Patrik J. Braun <bpatrik@users.noreply.github.com>
---------
Co-authored-by: Patrik J. Braun <bpatrik@users.noreply.github.com>
Without this, the mechanism to exclude a directory from indexing is a
bit strange. I had to use the `scanDirectory.after` hook, then remove
elements from the `output.directories` array.
In order to make the extension hook a bit more developer-friendly,
I also changed the arguments to the `excludeDir` function to be a
dictionary instead of just an array (or tuple?) of strings.
Allow for anonymous functions in logging calls.
The function is only called if the message is logged.
(e.g. if the verbosity is turned up high enough.)
This allows for expensive operations to be avoided
in cases where the logging won't happen.
The idea is that this provides a performance benefit.
I don't know how "expensive" an operation must be
to actually realize a performance benefit, though.
I added an example in server.ts...
It's probably "expensive" to dump the configuration
to JSON, then stringify that JSON for logging.
Added recognition of the offset value in the UI. It will be displayed if available.
Caveat: Search will not take offset into account. A new year's picture taken in Sydney the 1st of January 2019 00:15:00 GMT+11, is technically taken in 31st of December 2018 in UTC. Therefore this picture won't show of in seaches where the after: parameter is set to 1st of january 2019.
This is both correct and wrong at the same time.
UTC-wise it is correct, local time it is not correct. I guess most people would find local time most untuitive, so there is room for improvement of the search. :)
