activeadmin_addons 1.1.2 → 1.2.0

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/cucumber.yml

@@ -1,3 +0,0 @@
-default: --format 'progress' --require features/support/env.rb --require features/step_definitions features --tags ~@requires-reloading --tags ~@wip
-wip: --format 'progress' --require features/support/env.rb --require features/step_definitions features --tags @wip:3 --wip features
-class-reloading: RAILS_ENV=cucumber_with_reloading --format 'progress' --require features/support/env.rb --require features/step_definitions features --tags @requires-reloading

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/docs/0-installation.md

@@ -1,98 +0,0 @@
-# Installation
-
-Active Admin is a Ruby Gem.
-
-```ruby
-gem 'activeadmin'
-
-# Plus integrations with:
-gem 'devise'
-gem 'cancan' # or cancancan
-gem 'draper'
-gem 'pundit'
-```
-
-More accurately, it's a [Rails Engine](http://guides.rubyonrails.org/engines.html)
-that can be injected into your existing Ruby on Rails application.
-
-## Setting up Active Admin
-
-After installing the gem, you need to run the generator. By default we use Devise, and
-the generator creates an `AdminUser` model. If you want to create a different model
-(or modify an existing one for use with Devise) you can pass it as an argument.
-If you want to skip Devise configuration entirely, you can pass `--skip-users`.
-
-```sh
-rails g active_admin:install              # creates the AdminUser class
-rails g active_admin:install User         # creates / edits the class for use with Devise
-rails g active_admin:install --skip-users # skips Devise install
-```
-
-The generator adds these core files, among others:
-
-```
-app/admin/dashboard.rb
-app/assets/javascripts/active_admin.js.coffee
-app/assets/stylesheets/active_admin.scss
-config/initializers/active_admin.rb
-```
-
-Now, migrate your database and start the server:
-
-```sh
-rake db:migrate
-rails server
-```
-
-Visit `http://localhost:3000/admin` and log in as the default user:
-
-* __User__: admin@example.com
-* __Password__: password
-
-Voila! You're on your brand new Active Admin dashboard.
-
-To register an existing model with Active Admin:
-
-```sh
-rails generate active_admin:resource MyModel
-```
-
-This creates a file at `app/admin/my_model.rb` to set up the UI; refresh your browser to see it.
-
-# Upgrading
-
-When upgrading to a new version, it's a good idea to check the [CHANGELOG].
-
-To update the JS & CSS assets:
-
-```sh
-rails generate active_admin:assets
-```
-
-You should also sync these files with their counterparts in the AA source code:
-
-* app/admin/dashboard.rb [~>][dashboard.rb]
-* config/initializers/active_admin.rb [~>][active_admin.rb]
-
-# Gem compatibility
-
-## will_paginate
-
-If you use `will_paginate` in your app, you need to configure an initializer for
-Kaminari to avoid conflicts.
-
-```ruby
-# config/initializers/kaminari.rb
-Kaminari.configure do |config|
-  config.page_method_name = :per_page_kaminari
-end
-```
-
-## simple_form
-
-If you're getting the error `wrong number of arguments (6 for 4..5)`, [read #2703].
-
-[CHANGELOG]: https://github.com/activeadmin/activeadmin/blob/master/CHANGELOG.md
-[dashboard.rb]: https://github.com/activeadmin/activeadmin/blob/master/lib/generators/active_admin/install/templates/dashboard.rb
-[active_admin.rb]: https://github.com/activeadmin/activeadmin/blob/master/lib/generators/active_admin/install/templates/active_admin.rb.erb
-[read #2703]: https://github.com/activeadmin/activeadmin/issues/2703#issuecomment-38140864

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/docs/1-general-configuration.md

@@ -1,149 +0,0 @@
-# General Configuration
-
-You can configure Active Admin settings in `config/initializers/active_admin.rb`.
-Here are a few common configurations:
-
-## Authentication
-
-Active Admin requires two settings to authenticate and use the current user
-within your application.
-
-+ the method controllers used to force authentication
-
-```ruby
-config.authentication_method = :authenticate_admin_user!
-```
-
-+ the method used to access the current user
-
-```ruby
-config.current_user_method = :current_admin_user
-```
-
-Both of these settings can be set to false to turn off authentication.
-
-```ruby
-config.authentication_method = false
-config.current_user_method   = false
-```
-
-## Site Title Options
-
-Every page has what's called the site title on the left side of the menu bar.
-If you want, you can customize it.
-
-```ruby
-config.site_title       = "My Admin Site"
-config.site_title_link  = "/"
-config.site_title_image = "site_image.png"
-config.site_title_image = "http://www.google.com/images/logos/google_logo_41.png"
-config.site_title_image = ->(context) { context.current_user.company.logo_url }
-```
-
-## Internationalization (I18n)
-
-To translate Active Admin to a new language or customize an existing translation, you can copy
-[config/locales/en.yml](https://github.com/activeadmin/activeadmin/blob/master/config/locales/en.yml)
-to your application's `config/locales` folder and update it. We welcome new/updated translations,
-so feel free to [contribute](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md)!
-To translate third party gems like devise, use for example devise-i18n.
-
-## Localize Format For Dates and Times
-
-Active Admin sets `:long` as default localize format for dates and times.
-If you want, you can customize it.
-
-```ruby
-config.localize_format = :short
-```
-
-## Namespaces
-
-When registering resources in Active Admin, they are loaded into a namespace.
-The default namespace is "admin".
-
-```ruby
-# app/admin/posts.rb
-ActiveAdmin.register Post do
-  # ...
-end
-```
-
-The Post resource will be loaded into the "admin" namespace and will be
-available at `/admin/posts`. Each namespace holds on to its own settings that
-inherit from the application's configuration.
-
-For example, if you have two namespaces (`:admin` and `:super_admin`) and want to
-have different site title's for each, you can use the `config.namespace(name)`
-block within the initializer file to configure them individually.
-
-```ruby
-ActiveAdmin.setup do |config|
-  config.site_title = "My Default Site Title"
-
-  config.namespace :admin do |admin|
-    admin.site_title = "Admin Site"
-  end
-
-  config.namespace :super_admin do |super_admin|
-    super_admin.site_title = "Super Admin Site"
-  end
-end
-```
-
-Each setting available in the Active Admin setup block is configurable on a per
-namespace basis.
-
-## Load paths
-
-By default Active Admin files go inside `app/admin/`. You can change this
-directory in the initializer file:
-
-```ruby
-ActiveAdmin.setup do |config|
-  config.load_paths = [File.join(Rails.root, "app", "ui")]
-end
-```
-
-## Comments
-
-By default Active Admin includes comments on resources. Sometimes, this is
-undesired. To disable comments:
-
-```ruby
-# For the entire application:
-ActiveAdmin.setup do |config|
-  config.comments = false
-end
-
-# For a namespace:
-ActiveAdmin.setup do |config|
-  config.namespace :admin do |admin|
-    admin.comments = false
-  end
-end
-
-# For a given resource:
-ActiveAdmin.register Post do
-  config.comments = false
-end
-```
-
-## Utility Navigation
-
-The "utility navigation" shown at the top right normally shows the current user
-and a link to log out. However, the utility navigation is just like any other
-menu in the system; you can provide your own menu to be rendered in its place.
-
-```ruby
-ActiveAdmin.setup do |config|
-  config.namespace :admin do |admin|
-    admin.build_menu :utility_navigation do |menu|
-      menu.add label: "ActiveAdmin.info", url: "http://www.activeadmin.info",
-                                          html_options: { target: :blank }
-      admin.add_current_user_to_menu  menu
-      admin.add_logout_button_to_menu menu
-    end
-  end
-end
-```

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/docs/10-custom-pages.md

@@ -1,106 +0,0 @@
-# Custom Pages
-
-If you have data you want on a standalone page that isn't tied to a resource,
-custom pages provide you with a familiar syntax and feature set:
-
-* a menu item
-* sidebars
-* action items
-* page actions
-
-## Create a new Page
-
-Creating a page is as simple as calling `register_page`:
-
-```ruby
-# app/admin/calendar.rb
-ActiveAdmin.register_page "Calendar" do
-  content do
-    para "Hello World"
-  end
-end
-```
-
-Anything rendered within `content` will be the main content on the page.
-Partials behave exactly the same way as they do for resources:
-
-```ruby
-# app/admin/calendar.rb
-ActiveAdmin.register_page "Calendar" do
-  content do
-    render partial: 'calendar'
-  end
-end
-
-# app/views/admin/calendar/_calendar.html.arb
-table do
-  thead do
-    tr do
-      %w[Sunday Monday Tuesday Wednesday Thursday Friday Saturday].each &method(:th)
-    end
-  end
-  tbody do
-    # ...
-  end
-end
-```
-
-## Customize the Menu
-
-See the [Menu](2-resource-customization.md#customize-the-menu) documentation.
-
-## Customize the breadcrumbs
-
-```ruby
-ActiveAdmin.register_page "Calendar" do
-  breadcrumb do
-    ['admin', 'calendar']
-  end
-end
-```
-
-## Customize the Namespace
-
-We use the `admin` namespace by default, but you can use anything:
-
-```ruby
-# Available at /today/calendar
-ActiveAdmin.register_page "Calendar", namespace: :today
-
-# Available at /calendar
-ActiveAdmin.register_page "Calendar", namespace: false
-```
-
-## Add a Sidebar
-
-See the [Sidebars](7-sidebars.md) documentation.
-
-## Add an Action Item
-
-Just like other resources, you can add action items. The difference here being that
-`:only` and `:except` don't apply because there's only one page it could apply to.
-
-```ruby
-action_item :view_site do
-  link_to "View Site", "/"
-end
-```
-
-## Add a Page Action
-
-Page actions are custom controller actions (which mirror the resource DSL for the same feature).
-
-```ruby
-page_action :add_event, method: :post do
-  # ...
-  redirect_to admin_calendar_path, notice: "Your event was added"
-end
-
-action_item :add do
-  link_to "Add Event", admin_calendar_add_event_path, method: :post
-end
-```
-
-This defines the route `/admin/calendar/add_event` which can handle HTTP POST requests.
-
-Clicking on the action item will reload page and display the message "Your event was added"

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/docs/11-decorators.md

@@ -1,55 +0,0 @@
-# Decorators
-
-Active Admin allows you to use the decorator pattern to provide view-specific
-versions of a resource. [Draper](https://github.com/drapergem/draper) is
-recommended but not required.
-
-To use decorator support without Draper, your decorator must support a variety
-of collection methods to support pagination, filtering, etc. See
-[this github issue discussion](https://github.com/activeadmin/activeadmin/issues/3600)
-and [this gem](https://github.com/kiote/activeadmin-poro-decorator) for more details.
-
-## Example usage
-
-```ruby
-# app/models/post.rb
-class Post < ActiveRecord::Base
-  # has title, content, and image_url
-end
-
-# app/decorators/post_decorator.rb
-class PostDecorator < Draper::Decorator
-  delegate_all
-
-  def image
-    h.image_tag model.image_url
-  end
-end
-
-# app/admin/post.rb
-ActiveAdmin.register Post do
-  decorate_with PostDecorator
-
-  index do
-    column :title
-    column :image
-    actions
-  end
-end
-```
-
-## Forms
-
-By default, ActiveAdmin does *not* decorate the resource used to render forms.
-If you need ActiveAdmin to decorate the forms, you can pass `decorate: true` to the
-form block.
-
-```ruby
-ActiveAdmin.register Post do
-  decorate_with PostDecorator
-
-  form decorate: true do |f|
-    # ...
-  end
-end
-```

data/vendor/bundle/ruby/2.3.0/bundler/gems/activeadmin-a5a53c3f2b8f/docs/12-arbre-components.md

@@ -1,150 +0,0 @@
-# Arbre Components
-
-Arbre allows the creation of shareable and extendable HTML components and is
-used throughout Active Admin to create view components.
-
-## Text Node
-
-Sometimes it makes sense to insert something into a registered resource like a
-non-breaking space or some text. The text_node method can be used to insert
-these elements into the page inside of other Arbre components or resource
-controller functions.
-
-```ruby
-ActiveAdmin.register Post do
-  show do
-    panel "Post Details" do
-      attributes_table_for post do
-        row :id
-        row 'Tags' do
-          post.tags.each do |tag|
-            a tag, href: admin_post_path(q: {tagged_with_contains: tag})          
-            text_node " ".html_safe
-          end
-        end
-      end
-    end
-  end
-end
-```
-
-## Panels
-
-A panel is a component that takes up all available horizontal space and takes a
-title and a hash of attributes as arguments. If a sidebar is present, a panel
-will take up the remaining space.
-
-This will create two stacked panels:
-
-```ruby
-show do
-  panel "Post Details" do
-    render partial: "details", locals: {post: post}
-  end
-
-  panel "Post Tags" do
-    render partial: "tags",    locals: {post: post}
-  end
-end
-```
-
-## Columns
-
-The Columns component allows you draw content into scalable columns. All you
-need to do is define the number of columns and the component will take care of
-the rest.
-
-#### Simple Columns
-
-To create simple columnns, use the `columns` method. Within the block, call
-the #column method to create a new column.
-
-```ruby
-columns do
-  column do
-    span "Column #1"
-  end
-
-  column do
-    span "Column #2"
-  end
-end
-```
-
-### Spanning Multiple Columns
-
-To create columns that have multiple spans, pass the :span option to the column
-method.
-
-```ruby
-columns do
-  column span: 2 do
-    span "Column # 1"
-  end
-  column do
-    span "Column # 2"
-  end
-end
-```
-
-By default, each column spans 1 column. The above layout would have 2 columns,
-the first being twice as large as the second.
-
-### Custom Column Widths
-
-Active Admin uses a fluid width layout, causing column width to be defined
-using percentages. Due to using this style of layout, columns can shrink or
-expand past points that may not be desirable. To overcome this issue,
-columns provide `:max_width` and `:min_width` options.
-
-```ruby
-columns do
-  column max_width: "200px", min_width: "100px" do
-    span "Column # 1"
-  end
-  column do
-    span "Column # 2"
-  end
-end
-```
-
-In the above example, the first column will not grow larger than 200px and will
-not shrink less than 100px.
-
-## Table For
-
-Table For provides the ability to create tables like those present
-in `index_as_table`. It takes a collection and a hash of options and then
-uses `column` to build the fields to show with the table.
-
-```ruby
-table_for order.payments do
-  column(:payment_type) { |payment| payment.payment_type.titleize }
-  column "Received On",     :created_at
-  column "Details & Notes", :payment_details
-  column "Amount",          :amount_in_dollars
-end
-```
-
-the `column` method can take a title as its first argument and data
-(`:your_method`) as its second (or first if no title provided). Column also
-takes a block.
-
-## Status tag
-
-Status tags provide convenient syntactic sugar for styling items that have
-status. A common example of where the status tag could be useful is for orders
-that are complete or in progress. `status_tag` takes a status, like
-"In Progress", a type, which defaults to nil, and a hash of options. The
-status_tag will generate html markup that Active Admin css uses in styling.
-
-```ruby
-status_tag 'In Progress'
-# => <span class='status_tag in_progress'>In Progress</span>
-
-status_tag 'active', :ok
-# => <span class='status_tag active ok'>Active</span>
-
-status_tag 'active', :ok, class: 'important', id: 'status_123', label: 'on'
-# => <span class='status_tag active ok important' id='status_123'>on</span>
-```