<commit_before># mongo-seed
A build with testing MEAN applications in mind. Allow a developer to write the test data for and populate the database then tear it down.

## Reason for Existence

I built this to help with testing MEAN stack applications. So, you may be asking "Why did you do this?" or "Why not use RAKE?" 
or "Why not use another packages that do something similar?". My answer is part "I couldn't find exactly what I needed" and 
part "It sounded fun to write my own package to do this". 

To explain the first part more I will break down in to my use cases. 

1. Specific Test Data sets
   - I want to different types of data source to version data for specific tests. See seed types of what I wanted.
2. Precise control on data for specific states
   - See point 1 then add the ability to write functions to set up data.
3. Able to export just collections from mongodb 
    - I liked using mongoexport to get certain collections of data of only want I need.
4. Load multiple Databases
    - This is the one that really sold me. I wanted to be able to stand up two isolated databases with specific data sets
5. Readable seeds
    - Since the seeds can be super lean and in readable JSON it should be easy to manipulate them to fit test cases.
6. I like even number lists or lists that end at 3.
    - Don't Judge me

To explain the second part more...it sounded fun and it was.

TL;DR: I wanted it my way and I wanted to do it. I wonder if these are supposed to go at the top...

## Types of Seeds<commit_msg>Updating README for spelling errors...need sleep before working on this stuff<commit_after># mongo-seed
A build with testing MEAN applications in mind. Allow a developer to write the test data for and populate the database then tear it down.

## Reason for Existence

I built this to help with testing MEAN stack applications. So, you may be asking "Why did you do this?" or "Why not use RAKE?" 
or "Why not use another packages that do something similar?". My answer is part "I couldn't find exactly what I needed" and 
part "It sounded fun to write my own package to do this". 

To explain the first part more I will break down in to my use cases. 

1. Specific Test Data sets
   - Different types of data sources for versioned data on specific tests. See seed types of what I wanted.
2. Precise control on data for specific states
   - See point 1 then add the ability to write functions to set up data.
3. Able to export just collections from mongodb 
    - I liked using mongoexport to get certain collections of data of only want I need.
4. Load multiple Databases
    - This is the one that really sold me. I wanted to be able to stand up two isolated databases with specific data sets
5. Readable seeds
    - Since the seeds can be super lean and in readable JSON it should be easy to manipulate them to fit test cases.
6. I like even number lists or lists that end at 3.
    - Don't Judge me

To explain the second part more...it sounded fun and it was.

TL;DR: I wanted it my way and I wanted to do it. I wonder if these are supposed to go at the top...

## Types of Seeds
{'fraction_non_alphanumeric': 0.03958802703572578, 'fraction_numerical': 0.005149662053427744, 'mean_word_length': 3.322670375521558, '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': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '550195', 'n_tokens_mistral': 812, 'n_tokens_neox': 782, 'n_words': 564}