<commit_before>= has_messages

+has_messages+ demonstrates a reference implementation for sending messages between users.

== Resources

API

* http://rdoc.info/github/pluginaweek/has_messages/master/frames

Bugs

* http://pluginaweek.lighthouseapp.com/projects/13274-has_messages

Development

* http://github.com/pluginaweek/has_messages

Source

* git://github.com/pluginaweek/has_messages.git

== Description

Messaging between users is fairly common in web applications, especially those
that support social networking.  Messaging doesn't necessarily need to be
between users, but can also act as a way for the web application to send notices
and other notifications to users.

Designing and building a framework that supports this can be complex and takes
away from the business focus.  This plugin can help ease that process by
demonstrating a reference implementation of these features.

== Usage

=== Installation

+has_messages+ requires additional database tables to work.  You can generate
a migration for these tables like so:
<commit_msg>Use GitHub instead of Lighthouse for issue tracking<commit_after>= has_messages

+has_messages+ demonstrates a reference implementation for sending messages between users.

== Resources

API

* http://rdoc.info/github/pluginaweek/has_messages/master/frames

Bugs

* http://github.com/pluginaweek/has_messages/issues

Development

* http://github.com/pluginaweek/has_messages

Source

* git://github.com/pluginaweek/has_messages.git

== Description

Messaging between users is fairly common in web applications, especially those
that support social networking.  Messaging doesn't necessarily need to be
between users, but can also act as a way for the web application to send notices
and other notifications to users.

Designing and building a framework that supports this can be complex and takes
away from the business focus.  This plugin can help ease that process by
demonstrating a reference implementation of these features.

== Usage

=== Installation

+has_messages+ requires additional database tables to work.  You can generate
a migration for these tables like so:

{'fraction_non_alphanumeric': 0.05688763516690174, 'fraction_numerical': 0.0023507287259050304, 'mean_word_length': 4.96078431372549, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7405969', 'n_tokens_mistral': 558, 'n_tokens_neox': 529, 'n_words': 239}