This repository has been archived by the owner on Sep 7, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to our recent work on ingredient handlers, we've done some refactoring. But it's been a bit incomplete, leading to inconsistencies in the way we've organized them. This is a first step toward making it more obvious where ingredient handlers come from and how they're composed.
Unfortunately, this leads to a bit of a grab bag of changes. I tried to show some restraint though. The changes that happened here:
prose
handlers now reuse thesectionHandler
code used in other ingredients. 9c51c10 makes the change and 640c754 moves them alongside another handler wrapper. This is probably the most substantial thing, since it trims some duplicate code.sectionHandler
etc. See ddc64e8.There's more to be done, but this is a start.