Repository navigation
Allow passing HTTP and S3 URLs to --dictionaries #111
Description
The reason for this issue is that i work with several projects and i have a dictionary for each one.
But this dictionaries are very similar between to each others, and i need add de same words in all of them.
i think if the dictionary is stored in HTTP GET/POST URL, i can update a single dictionary and reuse it as long as it takes
Another option is an S3 standard, like AWS S3, Digitalocean Spaces o Minio bucket.
Right now i can't develop this topic because i don't have free time... in some free time i'll start doing it if i's not ready yet.
Activity
tbroadley commentedon Feb 3, 2023
I think this is a reasonable idea! I would accept a PR that changed the
--dictionariesargument to accept HTTP and S3 URLs as well as file paths.[-]Allow to save dictionary by HTTP method or S3 standard compatible[/-][+]Allow passing HTTP and S3 URLs to `--dictionaries`[/+]tbroadley commentedon Oct 19, 2024
It also seems reasonable to me for each project to download the dictionary using another tool, then call Spellchecker with the
--dictionariesargument pointing to the path of the downloaded dictionary.Apkahym commentedon Oct 21, 2024
This is a default feature with a user-scoped dictionary. I solved this with a Git sub-module, but this is a workaround. I'm working on my own version because this project is under-maintained and didn't add many useful features recently.
Thank you for your feedback
(S3 require more attributes than a single url to work safely)
tbroadley commentedon Oct 21, 2024
I'm going to reopen this because I think it represents a reasonable enhancement to this project.
If you've published your project, or will in the future, please share a link!