Add spellcheck support

[zez9787]

Current behavior

The current version does not support spellcheck.

Expected behavior

It would nice to have spellcheck support as a feature toggle in preferences. This issue was already created on the regular version of BoostNote Issue Here.

Steps to reproduce

Type any misspelled word.

Environment

Desktop/Web

• Boost Note.next version: 0.10.2
• OS version and name: Windows 10

---

IssueHunt Summary

Backers (Total: $50.00)

• boostio ($50.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[Rokt33r]

Electron itself should provide a spellchecker now so we can enable it quite easily.

https://www.electronjs.org/docs/tutorial/spellchecker

[issuehunt-oss]

@boostio has funded $50.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[liu971227-sys]

PR submitted: #1617

This implements the IssueHunt bounty request (spellcheck
support) by enabling Chromium spellchecker in the Electron app:

• BrowserWindow webPreferences: spellcheck: true
• BoostHub webpreferences: spellcheck=yes

This
makes the built-in spellchecker available; editor behavior can still be controlled via app settings/attributes.

[nicepopo86-lang]

I opened a PR for this: https://github.com/BoostIO/BoostNote-App/pull/1618\n\nIt enforces spellcheck attributes directly on the CodeMirror contenteditable input and keeps them in sync with the setting.

[nicepopo86-lang]

Follow-up clarification: the PR keeps the spellcheck behavior synced with the settings toggle key general.enableSpellcheck by applying attributes directly on the CodeMirror contenteditable input.

[lmee]

I read "Add spellcheck support" end-to-end and went through the full thread.

Problem I see: <!-- Issuehunt Badges --.
Root-cause hypothesis: a stale-state race between optimistic updates and confirmed data.
First patch plan: reproduce the issue against acceptance criteria, isolate the root cause in the relevant module, and submit a focused fix with regression tests.
If you want this path, I can share deterministic repro notes up front and then submit the minimal fix.