Lexicon-based not recursive analysis by line about evo-poster HOT 4 CLOSED

You can refer to specific issues in the commit message simply by inserting the number of the issue. It will help check what was actually done here.

from evo-poster.

✅ Lexicon global analysis is performed independently. (See nlp_utils/test.js).

from evo-poster.

I did not know. I'm still a little noob on GitHub. Today, I took some time read about conventional naming for commits. From now on I'll use Angular Commit Message Format, including the issue in the end of header

from evo-poster.

That is fine, but a minimalist approach to that is also OK. It's important that the first line only has 50 characters, so that it's not split by the GitHub interface (also, that's the convention for git log and all that), and that it includes the issue you're working with (so that it's easy to click and understand the context of the code that's been created). The rest is OK, but probably unnecessary

from evo-poster.