<commit_before>== preferences

+preferences+ adds support for easily creating custom preferences for models.

== Resources

API

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

Bugs

* http://pluginaweek.lighthouseapp.com/projects/13286-preferences

Development

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

Source

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

== Description

Preferences for models within an application, such as for users, is a pretty
common idiom.  Although the rule of thumb is to keep the number of preferences<commit_msg>Use GitHub instead of Lighthouse for issue tracking<commit_after>== preferences

+preferences+ adds support for easily creating custom preferences for models.

== Resources

API

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

Bugs

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

Development

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

Source

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

== Description

Preferences for models within an application, such as for users, is a pretty
common idiom.  Although the rule of thumb is to keep the number of preferences
{'fraction_non_alphanumeric': 0.0842745438748914, 'fraction_numerical': 0.004344048653344918, 'mean_word_length': 4.847715736040609, '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': '4837770', 'n_tokens_mistral': 332, 'n_tokens_neox': 319, 'n_words': 104}