Karl
FRACTALS! Here is mandelbrot fractal, and what you have in a nested object, the same function is applied in the big things, and in the little things with complex outcomes....
I can tackle this issue.
Another solution that will avoid modifying `RepoSettings` and `CommitFormatToml` structs is to simply use the error thrown upon parsing the `toml` file, and fallback `model` and `branch` to their default...
Don't worry, I am not in a hurry. EDIT: Yes, I've run `cargo fmt` and it automatically linted the code and now it is passing. ~I ran the `cargo fmt`...
A PR with a solution is proposed here: https://github.com/yewstack/yew-wasm-pack-template/pull/39
I completed the items on the checklist. I don't know if I need to squash more commits, and I don't know either how to fix de rubocop metrics related to...
Is there any cop similar to this, but to alert if you are using: `config[:root_key][:nested_key]` and suggest you to do: `config.dig(:root_key, :nested_key)` I used rubocop version 1.59.0 and didn't raise...
Yes @ydakuka there is a different behavior, thus it should not be auto corrected. My intention with that cop is -if it enabled- it will warn the developer: hey! you...
Sounds convincing... also, in my case rubocop will have to _infer_ the variable is a hash in order to raise the warning. Making suggestions about the type of variables you...
Is this the [config file](https://github.com/mlange-42/git-graph/blob/9bd54eb0aed6f108364bce9ad0bdff12077038fc/src/main.rs#L22) you want to store all permanent settings?