Jack Bates
Jack Bates
@ChristianMurphy Thank you for the encouragement! I started out aiming to give rules access to `settings` --- but to actually fix https://github.com/remarkjs/remark-lint/issues/263#issuecomment-903311532, I additionally made the remark-lint-emphasis-marker and remark-lint-strong-marker options...
unified-engine [passes `options` and `fileSet`](https://github.com/unifiedjs/unified-engine/blob/main/doc/plugins.md) to the attacher function. Plugins use it. With this change, rules can too?
I've added a commit to make the remaining rules' options default to their respective settings.
I've added https://github.com/remarkjs/remark-lint/pull/282 and a commit so that the presets respect `settings`, same as the rules.
It's not clear why the casting is unsafe?
@sandersn My understanding is, if it's a new clone (no project lockfiles) there's effectively no difference: - `latest` will resolve to the `latest` tag. That's the max non-prerelease by DT-tools...
@dscho Thanks a lot for your help! I've now signed-off. :heavy_check_mark:
:+1: Will do: I've replaced `tmux.until { |lines| lines[-1] == '$' }` with `tmux.prepare` and split apart changes that stand on their own.