You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could something similar be implemented, either in core or as an add-on / "extra word splitting layer", in spellbook? :) This is naturally quite useful for developers :) .
The text was updated successfully, but these errors were encountered:
That part of Spellbook is left to consuming applications. Spellbook assumes that the input for Dictionary::check or Dictionary::suggest is a single word. There is some basic case handling to make sure that proper nouns are correct only when titlecased, for example "Alice" but not "alice" in en_US, but splitting camel case words into separate tokens I would consider out of scope. It's hard to write a tokenization strategy that works for everyone and I want Spellbook to be very thin so I've left this to consumers. But CSpell's strategies are probably worth looking into for figuring out how we should tokenize in the Helix integration (#1).
I use cspell quite a bit and it has simple (but effective) logics implemented around:
See:
Could something similar be implemented, either in core or as an add-on / "extra word splitting layer", in spellbook? :) This is naturally quite useful for developers :) .
The text was updated successfully, but these errors were encountered: