Douglas Duhaime

@43081j have you tried codesandbox? Why don't you want a local build system?

@Haroenv I'm seeing this issue too. Just to check, is `autocomplete` (as distinct from `autocomplete.js`) compatible with `algoliasearch` v4? If not, what is the simplest path forward for someone with...

I ended up resolving this by simply rewinding my `package.json` so it contained: ``` "dependencies": { "algoliasearch": "^3.32.0", } ``` (The old version of algoliasearch used elsewhere in my app.)...

Yes absolutely in the long term everything should be on v4...

I've been playing around with primitive and Three.js to make some crazy little scenes of famous paintings:  https://bl.ocks.org/duhaime/6f2a71a76091162c57f66ea9e04db407

@michael-brade could you say a little about why the empty `documentclasses` folder is present? Can the repo be shipped without that directory (perhaps the directory could be used later when...

I needed to leave punctuation, and essentially just re-added it to my words after correcting their spelling: ```python import pkg_resources, string from symspellpy import SymSpell, Verbosity spell = SymSpell(max_dictionary_edit_distance=2, prefix_length=7)...

The PR looks great @julienbourdeau! It's letting me refrain from duplicating thousands of lines of attribution declarations. Thank you! This should be merged into the gem. I tried to ping...

There is an open pull request that will prevent users from having to duplicate attribute declarations: https://github.com/algolia/algoliasearch-rails/pull/335

@asadovsky Thanks for this! I'm still seeing unlinked dependencies though--did you actually compile on OSX with this branch, or do you have other changes that you didn't push?