Continue (from 9c4fc0b6866102217c165b87f1f97739fe2d2103) to prepare for the new con4m, by refactoring so that we get/set everything using the top-level chalk scope with fully-dotted keys. That helps prepare for the new con4m lookup interface, which at least in con4m v2 is:
I previously had about 20 more reviewable, self-contained and test-passing commits for this PR, but there were too many tricky conflicts with main, and I'd lost context on this part of the branch. So unfortunately it was best to squash before rebasing this on main, to reduce the time spent and bugs introduced when resolving conflicts.
CHANGELOG.md
if necessaryIssue
269
Description
Continue (from 9c4fc0b6866102217c165b87f1f97739fe2d2103) to prepare for the new con4m, by refactoring so that we get/set everything using the top-level chalk scope with fully-dotted keys. That helps prepare for the new con4m lookup interface, which at least in con4m v2 is:
where
key
is fully-dotted. And similarly in libcon4m:Before this PR we were passing subscopes around, and my understanding was that in the new con4m:
AttrScope
.Later we can try to:
I previously had about 20 more reviewable, self-contained and test-passing commits for this PR, but there were too many tricky conflicts with
main
, and I'd lost context on this part of the branch. So unfortunately it was best to squash before rebasing this onmain
, to reduce the time spent and bugs introduced when resolving conflicts.With this PR:
Bad hack for trying to find missing dots: