Open suchow opened 9 years ago
Related to your comment on alex, yes, we should definitely talk :)
Is there any reason why retext couldn’t be used? The power of retext is its plug-ability and composability. For example, alex itself is just a small shell over retext with the retext-equality plug-in!
One of the main reasons to not use retext directly is that retext is a javascript library. Proselint is built on python and shell scripts. The problem with javascript(ECMAscript) is that it would require bolting on more infrastructure than is desirable; namely for people to run it locally would require installing and running a node.js instance, which is way out of scope.
If you can figure out a good way to port the functionality of retext & the retext plugin infrastructure to python, then we can maybe try to figure it out. But otherwise we'll need to just focus on extracting the rules from js-based projects.
On Sun, Oct 25, 2015 at 5:50 AM, Titus Wormer notifications@github.com wrote:
Related to your comment on alex https://github.com/wooorm/alex/issues/54#issuecomment-150319218, yes, we should definitely talk :)
Is there any reason why retext couldn’t be used? The power of retext is its plug-ability and composability. For example, alex itself is just a small shell over retext with the retext-equality plug-in!
— Reply to this email directly or view it on GitHub https://github.com/amperser/proselint/issues/245#issuecomment-150920279.
Ah it's a language issue! Well, I of course prefer JS but I don't want to get in an argument Haha :wink:
https://github.com/wooorm/retext