<commit_before>[![Build Status](https://secure.travis-ci.org/tent/omniauth-tent.png)](http://travis-ci.org/tent/omniauth-tent)

# Omniauth::Tent

Omniauth strategy for Tent.

## Installation

Add this line to your application's Gemfile:

    gem 'omniauth-tent'


## Usage

```ruby
use OmniAuth::Builder do
  provider :tent, options
end
```

Available options (see [the Tent.io docs for details](http://tent.io/docs/app-auth))

| Option | Required | Description |
| ------ | -------- | ----------- |
| get_app_id | Yes | Should be a lambda (or anything which responds to `call`) returning either an existing app_id or `nil`. The entity URI will be passed in as a single argument. |
| on_app_created | Yes | Should respond to `call` and expect a single argument. It's called with app details when the app is first created (this happens when `get_app_id` returns `nil` or lookup fails for the given app_id) |
| app | Yes | `name`, `icon`, `url`, `description`, `scopes`, and `redirect_uris` |
| profile_info_types | Yes | Array of profile info type URIs your app wants access to |
| post_types | Yes | Array of post type URIs your app wants access to |
| notification_url | Yes | URL for receiving notifications |

## Testing

    bundle exec kicker

OR

    bundle exec rspec

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request<commit_msg>Add TODO list<commit_after>[![Build Status](https://secure.travis-ci.org/tent/omniauth-tent.png)](http://travis-ci.org/tent/omniauth-tent)

# Omniauth::Tent

Omniauth strategy for Tent.

## Installation

Add this line to your application's Gemfile:

    gem 'omniauth-tent'


## Usage

```ruby
use OmniAuth::Builder do
  provider :tent, options
end
```

Available options (see [the Tent.io docs for details](http://tent.io/docs/app-auth))

| Option | Required | Description |
| ------ | -------- | ----------- |
| get_app_id | Yes | Should be a lambda (or anything which responds to `call`) returning either an existing app_id or `nil`. The entity URI will be passed in as a single argument. |
| on_app_created | Yes | Should respond to `call` and expect a single argument. It's called with app details when the app is first created (this happens when `get_app_id` returns `nil` or lookup fails for the given app_id) |
| app | Yes | `name`, `icon`, `url`, `description`, `scopes`, and `redirect_uris` |
| profile_info_types | Yes | Array of profile info type URIs your app wants access to |
| post_types | Yes | Array of post type URIs your app wants access to |
| notification_url | Yes | URL for receiving notifications |

## Testing

    bundle exec kicker

OR

    bundle exec rspec

## Contributing

Here are some tasks that need to be done:

- Handle being passed an 'error' param in the callback_phase
- Find bugs and fix them

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
{'fraction_non_alphanumeric': 0.11981132075471698, 'fraction_numerical': 0.0031446540880503146, 'mean_word_length': 3.7195845697329375, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, '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': '5637983', 'n_tokens_mistral': 1004, 'n_tokens_neox': 953, 'n_words': 398}