Improve logic behind nested checklists

[spaghetti-coder]

Really love this nested checklists feature, not often used but handy in some cases. But there is a gap in my understanding of its logic.

Consider the list:

• Foo
  • Bar
  • Baz

When both Bar and Baz are checked Foo is forced to checked state either. Same applies to checking just Foo, it auto-checks all nested items. So Foo is union of Bar and Baz.
However there are 3 items in the progress bar, as if all 3 checkboxes are handled as separate units, but it's not so. There is no way to complete 2 tasks of 3, it's either 1 or all 3.

Depending on the feature design I can see 2 options here

1. Top level item is not considered as a separate task in terms of progress. I.e. the list above progress bar has only 2 items.
2. Progress items are still 3, but Bar and Baz checked doesn't force Foo to get checked, while checking Foo forces Bar and Baz check. I.e. Bar and Baz are part of Foo, but not the whole Foo

Option 1 seems more reasonable.

---

Really love you work. Thanks for the nice tool

[fccview]

I think 1 is definitely the option to go for!
May need to be next release, this one's pretty packed as you probably saw in the pull request haha

[spaghetti-coder]

Thanks. Will pick it if you don't mind

[fccview]

Thanks. Will pick it if you don't mind

All yours! 🤜🤛