feat: Deduplicate spelling errors, send only the first occurrence to diagnostics

[chaneyzorn]

For example, codebook will only show the spelling error at its first definition, not at the places where it is used.

[ravibrock]

I think this is an anti-feature; the goal of Spellwarn is to display Neovim's built-in spelling errors in a nicer way--I don't want to go away from that and start changing in the plugin which errors are displayed. Will take a look at your other issue when I have the chance.

[chaneyzorn]

Yes, this is indeed not a display scenario that fits well with nvim's built-in spellcheck.

Could we consider providing a universal hook mechanism—for example, allowing users to implement custom processing before calling vim.diagnostic.set?

One approach is to expose a configuration item of function type in the config,
and another is to trigger a User event.

vim.api.nvim_exec_autocmds("User", { pattern = "SpellWarnRefresh", data ={bufnr=.., diagnostics=..} })
-- Pre or Post suffix may need to be considered

[ravibrock]

I think that makes sense–use Spellwarn to collate spelling errors into a table, and then let users do what they want with those errors. Pretty busy right now, I'll try to take a closer look over my spring break (next week).

[coreyb-git]

Yes, this is indeed not a display scenario that fits well with nvim's built-in spellcheck.

Could we consider providing a universal hook mechanism—for example, allowing users to implement custom processing before calling vim.diagnostic.set?

One approach is to expose a configuration item of function type in the config, and another is to trigger a User event.

vim.api.nvim_exec_autocmds("User", { pattern = "SpellWarnRefresh", data ={bufnr=.., diagnostics=..} })
-- Pre or Post suffix may need to be considered

PR: #21

Adds a preprocess function option called before vim.diagnostic.set is called.

[coreyb-git]

Scratch that... PR #22

[github-actions]

Bump — this issue has had no activity for 7 days. This is a maintainer reminder so it doesn't get lost.