Better handling of missing files #3

New issue

Closed

opened 2020-02-05 11:23:13 +00:00 by liska · 0 comments

liska commented

2020-02-05 11:23:13 +00:00

Owner

config.yml
Enforce reasonable defaults
defaults.yml
This should only cause an exception if the template actually contains replacement fields. In addition the replacement fields should be tested for defaults. Each field must have a default value in the configuration (also because these defaults are used to control the actual replacement process
outline.yml
If this file is missing we should infer the outline from the books directory:
- Use the directories as subbooks in alphabetical order.
- if a main directory is present treat it as the main book.

Currently several cases of missing files will simply trigger exceptions. I assume that some errors in the configuration will even trigger unexpected exceptions. The following behaviour should be implemented: * [x] `config.yml` Enforce reasonable defaults * [ ] `defaults.yml` This should only cause an exception if the template actually contains replacement fields. In addition the replacement fields should be tested for defaults. Each field must have a default value in the configuration (also because these defaults are used to control the actual replacement process * [ ] `outline.yml` If this file is missing we should infer the outline from the `books` directory: - Use the directories as subbooks in alphabetical order. - if a `main` directory is present treat it as the main book.