This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of natural.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
668f858Cleaned up some code that became obsolete after changing the way in which a tagger is created.
75caa4fRefactored the tagger such that reading transformation rules and lexicon is external to the tagger object and can be implemented as you wish. Standard implementation for reading a lexicon file is provided. Also synchronous file I/O is used in order to simplify creation of lexicon and ruleset.
5bbff42Merge pull request #292 from jdesboeufs/master
c6e1a5eMerge pull request #293 from moklick/patch-1
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
natural just published its new version 0.5.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of natural. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 28 commits .
378ec2b0.5.0a1e0259Merge pull request #326 from handav/add-documentation9ce9dfaadding Egghead.io course documentation0edd9c2Merge pull request #321 from adrianmcli/remove-log4js05b3508comment out console.log to prevent verbose output055dc5bremove log4js and replace logger calls with native console.log or console.errorf97adfdremove log4js from package.json1231da1#284 update readme9e56c8fMerge branch 'Hugo-ter-Doest-master'7400a21merge READMEc72c05eUpdated the README for the changes.668f858Cleaned up some code that became obsolete after changing the way in which a tagger is created.75caa4fRefactored the tagger such that reading transformation rules and lexicon is external to the tagger object and can be implemented as you wish. Standard implementation for reading a lexicon file is provided. Also synchronous file I/O is used in order to simplify creation of lexicon and ruleset.5bbff42Merge pull request #292 from jdesboeufs/masterc6e1a5eMerge pull request #293 from moklick/patch-1There are 28 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.