<commit_before># Scriptures

This is a self contained copy of the LDS standard works as a ruby gem.

## Why?

Because I can.
Thinking about making a scriptures REST services out of it.
Maybe I am looking for a job at tech.lds.org? HAHA.

## Installation

Add this line to your application's Gemfile:

    gem 'scriptures'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install scriptures

## Dependancies

Needs sqlite engine installed. My preference on OSX is to install through homebrew with:

    $ brew install sqlite

## Usage Examples

    require 'scriptures'
    
    puts Scriptures::Verse.all(:scripture.like => "%faith%").first.scripture
    
    puts Scripures.search("faith").count

## TODO

* Make search improvements.
* Improve Readme and describe API


## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
<commit_msg>added more ideas for todos<commit_after># Scriptures

This is a self contained copy of the LDS standard works as a ruby gem.

## Why?

Because I can.
Thinking about making a scriptures REST services out of it.
Maybe I am looking for a job at tech.lds.org? HAHA.

## Installation

Add this line to your application's Gemfile:

    gem 'scriptures'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install scriptures

## Dependancies

Needs sqlite engine installed. My preference on OSX is to install through homebrew with:

    $ brew install sqlite

## Usage Examples

    require 'scriptures'
    
    puts Scriptures::Verse.all(:scripture.like => "%faith%").first.scripture
    
    puts Scripures.search("faith").count

## TODO

* Make search improvements.
* Improve Readme and describe API
* Maybe make some built in scopes (scripture mastery list etc)
* Eventually enable API for highlighting, notes and CLI


## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

{'fraction_non_alphanumeric': 0.0795863309352518, 'fraction_numerical': 0.0044964028776978415, 'mean_word_length': 3.568788501026694, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '436384', 'n_tokens_mistral': 675, 'n_tokens_neox': 633, 'n_words': 294}