Follow-up from "Parse task checkboxes in Markdown, part Ⅱ: The Checkboxening"
The following discussions from !219037 should be addressed: - [ ] @hfyngvason started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219037#note_3080860172): > **Not blocking:** Would it make sense to have one filter per task-list-type? - [ ] @hfyngvason started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/219037#note_3080860185): > **Non-blocking nit:** This is a bit noisy, makes it hard to spot mistakes. I like the "obviousness" of the code however. Not sure about improvements, maybe something like > > ```ruby > result[:start][:column] += adjust.dig(:start, :column).to_i > ``` > > or, a bit safer (avoiding implicit conversions) > > ```ruby > result[:start][:column] += (adjust.dig(:start, :column) || 0) > ```
issue