capybara_active_admin 1.0.0 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7734f257fe31b75bea9782d9c0cd24bc8591a0c05a9db0a0b7a6f264d8515b20
-  data.tar.gz: 5270545aa73089ac413bd1e1e250da449f795ffde996259b6f8d14c49476d257
+  metadata.gz: bafb813d42831673f3ea1a80e97e410b1dced0c55cdf4c043fbc24ff5fbcc11e
+  data.tar.gz: 6115f349a6204615861dd23f0b022c66086e72f9a054bc12a808858ac7824d38
 SHA512:
-  metadata.gz: 88319fec5e984e419f0dc3c130a49907f98aec9fd7f62560acdc276f10e2c670772f44198bf81e1439dc14bf3f0bf0a306b1aef22059427c14fdbdffe3a7c47d
-  data.tar.gz: 694336b60366c1a9ae9ca61e7df39370fd2e86eb242850c93faf0689663ebc827bd448e49f5fa238a7bb78377dc29fcdbfa4cabe2b9ee1081e4bdc039fe64b5b
+  metadata.gz: c2f006051d76bf7c4adc0d23e0098ff5ecf9703be0e11bf43d08301c06bd3770b23c85661218940c1ef60af8cad8a1306802436f6e85469ac2a7f436276559ae
+  data.tar.gz: 49557743c791ecfb6069a755771e47946ec0985627ee8c2b351bada208a38cd062ad65dff8c70f75d070f043c2cde102ff924d2ef5d5c680f20a85dad7513357

data/CHANGELOG.md

@@ -6,6 +6,54 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.0.0] - 2026-10-01
+
+Breaking: the selectors below build a different string than 1.0.0 did for the
+same input, so a suite that passed on 1.0.0 can fail on this version without
+changing a line.
+
+### Migrating from 1.0.0
+
+ - If you wrote a helper that normalized labels before handing them to
+   `table_cell_selector` / `table_header_selector` / `attributes_row_selector`,
+   delete it. The gem now makes the same `parameterize(separator: '_')` call
+   ActiveAdmin makes, so normalizing twice corrupts the result — the second
+   pass strips the `_` the first one inserted.
+ - Labels with no Latin-transliterable characters (`'Имя'`, `'名前'`, `'№'`)
+   now raise instead of silently matching every such row. Match on text, or
+   pass the attribute name.
+ - Rails 7.2 is no longer tested.
+
+### Fixed
+ - `attributes_table_selector`, `form_selector` and `table_selector` now ask the
+   model for its DOM name (`model_name.singular` / `.plural`, the same source
+   Arbre and ActiveAdmin use) instead of `gsub(' ', '_')`. A namespaced name
+   previously kept its `::` and produced `div.attributes_table.billing::employee`
+   — not a selector, so it aborted the example instead of failing it.
+   `table_selector` also accepts a model class now.
+
+### Changed
+ - `table_cell_selector`, `table_header_selector` and `attributes_row_selector`
+   now derive the CSS class with `parameterize(separator: '_')`, the same call
+   ActiveAdmin makes in `AttributesTable#row` and `TableFor::Column#html_class`,
+   instead of three different hand-rolled substitutions. Labels containing
+   punctuation change selector: `'E-mail'` was `col-email` and is now
+   `col-e-mail`, `"Customer's Name"` was `col-customers_name` and is now
+   `col-customer_s_name`, `:full_name` was `col-fullname` and is now
+   `col-full_name`. Previously these matched nothing (or raised
+   `Nokogiri::CSS::SyntaxError`), so an app carrying a workaround that
+   pre-normalized labels before calling these helpers should drop it.
+ - `table_header_selector(nil, column: 'x')` now honours the override instead
+   of returning the generic header selector.
+ - tested against Ruby 3.3, 3.4, 4.0 and Rails 8.0, 8.1 (EOL Rails 7.2 dropped from CI)
+
+### Fixed
+ - a label that `parameterize` cannot transliterate (`'Имя'`, `'名前'`, `'№'`, or
+   a blank string) now raises `ArgumentError` instead of building a bare
+   `.row-` / `.col-` selector. ActiveAdmin renders the same empty class for
+   every such label, so that selector matched all of them at once and the
+   matcher could pass against the wrong row.
+
 ## [1.0.0] - 2026-04-09
 
 ### Added
@@ -22,8 +70,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
  - `have_status_tag` matcher for status tag elements
 
 ### Changed
- - `within_sidebar` now scopes within the sidebar section directly using `ancestor`
- - `have_table_scope` now accepts an optional title as first positional argument and `selected:` keyword arg
+ - `have_table_scope` now accepts an optional title as first positional argument and `selected:` keyword arg.
+   **Breaking**, and not spelled out at the time: the `active:` key it replaced
+   is no longer consumed, so it falls through to `have_selector` and Capybara
+   rejects it with `ArgumentError: Invalid option(s) :active`. Rename
+   `active:` to `selected:`; the selector built is the same.
+ - `within_sidebar` now scopes within the sidebar section directly using `ancestor`.
+   **Breaking** for a block that relied on the old scope being the panel rather
+   than the whole `.sidebar_section`.
 
 ## [0.3.3] - 2020-04-17
 ### Changed

data/README.md

@@ -55,17 +55,17 @@ RSpec.describe 'Users', js: true do
 
     within_table_for('users') do
       expect(page).to have_table_row(count: 2)
-      expect(page).to have_table_cell('John Doe')
+      expect(page).to have_table_cell(text: 'John Doe')
 
       within_table_row(id: john.id) do
-        expect(page).to have_table_cell('John Doe', row_id: john.id)
-        expect(page).to have_table_cell('John Doe', row_id: john.id, col_name: 'Full Name')
-        expect(page).to_not have_table_cell('John Doe', row_id: john.id, col_name: 'Id')
+        expect(page).to have_table_cell(text: 'John Doe')
+        expect(page).to have_table_cell(text: 'John Doe', column: 'Full Name')
+        expect(page).to_not have_table_cell(text: 'John Doe', column: 'Id')
       end
 
       within_table_row(id: jane.id) do
-        expect(page).to_not have_table_cell('John Doe')
-        expect(page).to_not have_table_cell('John Doe', col_name: 'Full Name')
+        expect(page).to_not have_table_cell(text: 'John Doe')
+        expect(page).to_not have_table_cell(text: 'John Doe', column: 'Full Name')
       end
     end
   end
@@ -94,6 +94,67 @@ end
 See `spec/support` for more user examples.
 See `capybara/active_admin/test_helpers.rb` for available DSL methods.
 
+## How labels become selectors
+
+Most helpers take the label you see on the page and build a CSS selector from
+it, because that is how ActiveAdmin names its own elements. Two derivations are
+worth knowing, since a mismatch shows up as "element not found" with no hint of
+why.
+
+### Column and row labels
+
+ActiveAdmin builds the class with `parameterize(separator: '_')` —
+`AttributesTable#row` and `TableFor::Column#html_class` — and so does this gem:
+
+| label | class ActiveAdmin renders |
+| --- | --- |
+| `'Full Name'` | `col-full_name` |
+| `:full_name` | `col-full_name` |
+| `'VAT / TAX Number'` | `col-vat_tax_number` |
+| `'E-mail'` | `col-e-mail` |
+| `"Customer's Name"` | `col-customer_s_name` |
+| `'# of DIDs'` | `col-of_dids` |
+
+So pass the label as it appears, and do **not** normalize it yourself first —
+doing it twice strips the separator the first pass inserted.
+
+Two cases have no class to match:
+
+```ruby
+# ActiveAdmin renders class="row" with no row-* at all when you give your own
+row :salary, class: 'money'
+
+# parameterize drops everything non-Latin, so AA renders a bare class="row row-"
+# for every such label and they cannot be told apart. The gem raises rather
+# than match the wrong one.
+row 'Имя'
+```
+
+Match on text in both cases, or pass the attribute name rather than the label.
+
+### Model and resource names
+
+`have_attributes_table(model:)` and `within_form_for` follow the **model
+class** — Arbre uses `model_name.singular`:
+
+```ruby
+have_attributes_table(model: Billing::Employee)     # div.attributes_table.billing_employee
+have_attributes_table(model: 'Billing::Employee')   # same
+```
+
+`have_table(resource_name:)` and `within_table_for` follow the name the
+resource was **registered** under, which `as:` detaches from the model:
+
+```ruby
+ActiveAdmin.register Billing::Employee, as: 'Business Employee'
+
+within_table_for('Business Employee') { ... }   # table#index_table_business_employees
+within_table_for(Billing::Employee)   { ... }   # table#index_table_billing_employees -- wrong
+```
+
+A renamed resource has to be addressed by its registered name; the class cannot
+know it.
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/lib/capybara/active_admin/selectors/attributes_table.rb

@@ -1,5 +1,7 @@
 # frozen_string_literal: true
 
+require 'capybara/active_admin/util'
+
 module Capybara
   module ActiveAdmin
     module Selectors
@@ -18,7 +20,7 @@ module Capybara
         def attributes_row_selector(label = nil)
           return 'tr.row > td' if label.nil?
 
-          label = label.to_s.gsub(/[\s\/]/, '_').downcase
+          label = Util.css_class_for_label(label)
           "tr.row.row-#{label} > td"
         end
       end

data/lib/capybara/active_admin/selectors/table.rb

@@ -1,5 +1,7 @@
 # frozen_string_literal: true
 
+require 'capybara/active_admin/util'
+
 module Capybara
   module ActiveAdmin
     module Selectors
@@ -10,8 +12,12 @@ module Capybara
         def table_selector(resource_name = nil)
           return 'table.index_table' if resource_name.nil?
 
-          resource_name = resource_name.to_s.gsub(' ', '_').pluralize.downcase
-          "table#index_table_#{resource_name}"
+          # NOTE: ActiveAdmin builds this id from the registered resource name
+          # (`active_admin_config.resource_name.plural`, index_as_table.rb:240),
+          # which `register Model, as: 'Other Name'` detaches from the model.
+          # A class can only ever yield the model's own name, so a renamed
+          # resource has to be addressed by the name it was registered under.
+          "table#index_table_#{Util.parse_model_name(resource_name, singular: false)}"
         end
 
         # @param record_id [String, Integer, nil] record ID.
@@ -29,9 +35,9 @@ module Capybara
         # @option sort_direction [String, nil] sort direction ('asc' or 'desc').
         # @return selector.
         def table_header_selector(text = nil, options = {})
-          return 'thead > tr > th.col' if text.nil?
+          return 'thead > tr > th.col' if text.nil? && options[:column].nil?
 
-          column = (options[:column] || text).to_s.tr(' ', '_').downcase
+          column = Util.css_class_for_label(options[:column] || text)
           selector = "th.col.col-#{column}"
           selector += '.sortable' if options[:sortable]
           selector += ".sorted-#{options[:sort_direction].to_s.downcase}" if options[:sort_direction].present?
@@ -43,8 +49,7 @@ module Capybara
         def table_cell_selector(column = nil)
           return 'td.col' if column.nil?
 
-          # Downcase, strip non-alphanumeric chars (e.g. '/'), convert spaces to '_', deduplicate '_'
-          column = column.to_s.downcase.gsub(/[^a-z0-9\s]/, '').gsub(/\s+/, '_').squeeze('_')
+          column = Util.css_class_for_label(column)
           "td.col.col-#{column}"
         end
 

data/lib/capybara/active_admin/util.rb

@@ -5,12 +5,49 @@ module Capybara
     module Util
       # Common pure utility functions
 
+      # Arbre derives a record's DOM name from
+      # `record.class.model_name.singular`, falling back to
+      # `name.underscore.gsub('/', '_')` (arbre html/tag.rb:164-168). Ask the
+      # model the same question instead of approximating it: `gsub(' ', '_')`
+      # leaves the `::` of a namespaced name in place, and
+      # `div.attributes_table.billing::employee` is not a selector -- Nokogiri
+      # raises `SyntaxError` on it with nothing pointing at the cause.
       def parse_model_name(model_name, singular: true)
         return if model_name.nil?
 
-        model_name = model_name.model_name.singular if model_name.is_a?(Class)
-        model_name = model_name.to_s.gsub(' ', '_').downcase
-        singular ? model_name.singularize : model_name.pluralize
+        if model_name.is_a?(Class) && model_name.respond_to?(:model_name)
+          name = model_name.model_name
+          return singular ? name.singular : name.plural
+        end
+
+        dom_model_name(model_name.is_a?(Class) ? model_name.name : model_name, singular: singular)
+      end
+
+      def dom_model_name(name, singular: true)
+        name = name.to_s.underscore.tr('/', '_').tr(' ', '_')
+        singular ? name.singularize : name.pluralize
+      end
+
+      # ActiveAdmin derives the CSS class of a row or column from the
+      # label with `parameterize(separator: '_')` --
+      # `AttributesTable#row` and `TableFor::Column#html_class`. Mirror
+      # that call rather than approximating it, so every label lands on
+      # the class ActiveAdmin actually rendered.
+      def css_class_for_label(label)
+        css_class = label.to_s.parameterize(separator: '_')
+        return css_class if css_class.present?
+
+        # `parameterize` transliterates to Latin and drops the rest, so any
+        # label without Latin-transliterable characters -- 'Имя', '名前', '№',
+        # or a blank string -- comes back empty. ActiveAdmin makes the same
+        # call, so it renders `class="row row-"` for all of them, and a
+        # `.row-` selector would match every one at once: the matcher would
+        # pass against the wrong row instead of failing. Refuse to build it.
+        raise ArgumentError,
+              "cannot derive a CSS class from #{label.inspect}: " \
+              'ActiveAdmin parameterizes it to an empty string, so every such ' \
+              'row or column shares one class and cannot be told apart. ' \
+              'Match on text, or pass the attribute name instead of the label.'
       end
 
       def options_with_text(text, options = {})
@@ -19,7 +56,7 @@ module Capybara
         options.except(:exact).merge(key => text)
       end
 
-      module_function :parse_model_name, :options_with_text
+      module_function :parse_model_name, :dom_model_name, :css_class_for_label, :options_with_text
     end
   end
 end

data/lib/capybara/active_admin/version.rb

@@ -2,6 +2,6 @@
 
 module Capybara
   module ActiveAdmin
-    VERSION = '1.0.0'
+    VERSION = '2.0.0'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capybara_active_admin
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 2.0.0
 platform: ruby
 authors:
 - Denis Talakevich
@@ -50,25 +50,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".github/workflows/ci.yml"
-- ".github/workflows/codeql.yml"
-- ".gitignore"
-- ".rspec"
-- ".rubocop.yml"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- Gemfile
 - LICENSE.txt
 - README.md
-- Rakefile
-- bin/console
-- bin/setup
-- capybara_active_admin.gemspec
-- docs/.vuepress/config.js
-- docs/.vuepress/public/.keep
-- docs/.vuepress/styles/index.styl
-- docs/README.md
-- docs/guide/README.md
 - lib/capybara/active_admin.rb
 - lib/capybara/active_admin/actions.rb
 - lib/capybara/active_admin/actions/attributes_table.rb
@@ -95,7 +79,6 @@ files:
 - lib/capybara/active_admin/util.rb
 - lib/capybara/active_admin/version.rb
 - lib/capybara_active_admin.rb
-- package.json
 homepage: https://github.com/active_admin_plugins/capybara_active_admin
 licenses:
 - MIT

data/.github/workflows/ci.yml

@@ -1,88 +0,0 @@
-name: CI
-on:
-  pull_request:
-  push:
-    branches: [master]
-
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-jobs:
-  test:
-    name: Ruby ${{ matrix.ruby }} / Rails ${{ matrix.rails }} / AA ${{ matrix.activeadmin }}
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: ['3.3', '3.4', '4.0']
-        rails: ['~> 7.2.0', '~> 8.0.0', '~> 8.1.0']
-        activeadmin: ['~> 3.2', '~> 3.3', '~> 3.4', '~> 3.5']
-    env:
-      RAILS_VERSION: ${{ matrix.rails }}
-      ACTIVE_ADMIN_VERSION: ${{ matrix.activeadmin }}
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-          bundler-cache: true
-      - name: Run tests
-        run: bundle exec rspec spec
-
-      - name: Generate badge.json
-        if: matrix.ruby == '4.0' && matrix.rails == '~> 8.1.0' && matrix.activeadmin == '~> 3.5'
-        run: |
-          LAST_RUN="coverage/.last_run.json"
-          if [ ! -f "$LAST_RUN" ]; then
-            mkdir -p badge
-            echo '{"schemaVersion":1,"label":"coverage","message":"unknown","color":"lightgrey"}' > badge/badge.json
-            exit 0
-          fi
-          PERCENT=$(ruby -rjson -e "puts JSON.parse(File.read('$LAST_RUN')).dig('result','line').round(1)")
-          PERCENT_NUM=$(ruby -rjson -e "puts JSON.parse(File.read('$LAST_RUN')).dig('result','line')")
-          if ruby -e "exit(($PERCENT_NUM >= 90) ? 0 : 1)"; then COLOR="brightgreen"
-          elif ruby -e "exit(($PERCENT_NUM >= 75) ? 0 : 1)"; then COLOR="green"
-          elif ruby -e "exit(($PERCENT_NUM >= 60) ? 0 : 1)"; then COLOR="yellow"
-          else COLOR="red"; fi
-          mkdir -p badge
-          echo "{\"schemaVersion\":1,\"label\":\"coverage\",\"message\":\"${PERCENT}%\",\"color\":\"${COLOR}\"}" > badge/badge.json
-
-      - name: Upload badge artifact
-        if: matrix.ruby == '4.0' && matrix.rails == '~> 8.1.0' && matrix.activeadmin == '~> 3.5'
-        uses: actions/upload-artifact@v4
-        with:
-          name: coverage-badge
-          path: badge
-
-  deploy-coverage:
-    needs: test
-    if: github.ref == 'refs/heads/master' && github.event_name == 'push'
-    runs-on: ubuntu-latest
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: gh-pages
-
-      - name: Download coverage badge
-        uses: actions/download-artifact@v4
-        with:
-          name: coverage-badge
-          path: .
-
-      - name: Setup Pages
-        uses: actions/configure-pages@v5
-
-      - name: Upload Pages artifact
-        uses: actions/upload-pages-artifact@v3
-        with:
-          path: .
-
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4

data/.github/workflows/codeql.yml

@@ -1,104 +0,0 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-# ******** NOTE ********
-# We have attempted to detect the languages in your repository. Please check
-# the `language` matrix defined below to confirm you have the correct set of
-# supported CodeQL languages.
-#
-name: "CodeQL Advanced"
-
-on:
-  push:
-    branches: [ "master" ]
-  pull_request:
-    branches: [ "master" ]
-  schedule:
-    - cron: '38 15 * * 0'
-
-jobs:
-  analyze:
-    name: Analyze (${{ matrix.language }})
-    # Runner size impacts CodeQL analysis time. To learn more, please see:
-    #   - https://gh.io/recommended-hardware-resources-for-running-codeql
-    #   - https://gh.io/supported-runners-and-hardware-resources
-    #   - https://gh.io/using-larger-runners (GitHub.com only)
-    # Consider using larger runners or machines with greater resources for possible analysis time improvements.
-    runs-on: 'ubuntu-latest'
-    permissions:
-      # required for all workflows
-      security-events: write
-
-      # required to fetch internal or private CodeQL packs
-      packages: read
-
-      # only required for workflows in private repositories
-      actions: read
-      contents: read
-
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-        - language: actions
-          build-mode: none
-        - language: ruby
-          build-mode: none
-        # CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
-        # Use `c-cpp` to analyze code written in C, C++ or both
-        # Use 'java-kotlin' to analyze code written in Java, Kotlin or both
-        # Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
-        # To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
-        # see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
-        # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
-        # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
-    steps:
-    - name: Checkout repository
-      uses: actions/checkout@v4
-
-    # Add any setup steps before running the `github/codeql-action/init` action.
-    # This includes steps like installing compilers or runtimes (`actions/setup-node`
-    # or others). This is typically only required for manual builds.
-    # - name: Setup runtime (example)
-    #   uses: actions/setup-example@v1
-
-    # Initializes the CodeQL tools for scanning.
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v4
-      with:
-        languages: ${{ matrix.language }}
-        build-mode: ${{ matrix.build-mode }}
-        config: |
-          paths-ignore:
-            - '**/spec/**'
-        # If you wish to specify custom queries, you can do so here or in a config file.
-        # By default, queries listed here will override any specified in a config file.
-        # Prefix the list here with "+" to use these queries and those in the config file.
-
-        # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
-        # queries: security-extended,security-and-quality
-
-    # If the analyze step fails for one of the languages you are analyzing with
-    # "We were unable to automatically build your code", modify the matrix above
-    # to set the build mode to "manual" for that language. Then modify this step
-    # to build your code.
-    # ℹ️ Command-line programs to run using the OS shell.
-    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
-    - name: Run manual build steps
-      if: matrix.build-mode == 'manual'
-      shell: bash
-      run: |
-        echo 'If you are using a "manual" build mode for one or more of the' \
-          'languages you are analyzing, replace this with the commands to build' \
-          'your code, for example:'
-        echo '  make bootstrap'
-        echo '  make release'
-        exit 1
-
-    - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v4
-      with:
-        category: "/language:${{matrix.language}}"

data/.gitignore

@@ -1,21 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-/spec/dummy/tmp/
-/spec/dummy/log/*.log
-
-# rspec failure tracking
-.rspec_status
-
-Gemfile.lock
-
-# docs
-/docs/.vuepress/dist/
-/docs/.vuepress/public/api/
-/node_modules/
-yarn.lock

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---require rails_helper

data/.rubocop.yml

@@ -1,82 +0,0 @@
-AllCops:
-  DisplayCopNames: true
-  TargetRubyVersion: 2.3
-  Exclude:
-    - vendor/**/*
-    - tmp/**/*
-    - docs/**/*
-
-# Capybara/RSpec uses have_ had_ as name convention for matchers.
-Naming/PredicateName:
-  Enabled: false
-
-Lint/RaiseException:
-  Enabled: true
-
-Lint/StructNewOverride:
-  Enabled: true
-
-Layout/LineLength:
-  Max: 180
-
-Style/SymbolArray:
-  EnforcedStyle: brackets
-
-Style/Lambda:
-  EnforcedStyle: literal
-
-Naming/MethodParameterName:
-  AllowedNames:
-    - id
-
-Style/HashEachMethods:
-  Enabled: true
-
-Style/HashTransformKeys:
-  Enabled: true
-
-Style/HashTransformValues:
-  Enabled: true
-
-Style/Documentation:
-  Enabled: false
-
-Metrics/PerceivedComplexity:
-  Enabled: false
-
-Metrics/MethodLength:
-  Enabled: false
-
-Metrics/AbcSize:
-  Enabled: false
-
-Metrics/ModuleLength:
-  Enabled: false
-
-Metrics/BlockLength:
-  Enabled: false
-
-Metrics/ClassLength:
-  Enabled: false
-
-Metrics/CyclomaticComplexity:
-  Enabled: false
-
-Layout/MultilineOperationIndentation:
-  Enabled: false
-
-Layout/FirstHashElementIndentation:
-  Enabled: false
-
-Layout/FirstArrayElementIndentation:
-  Enabled: false
-
-Layout/FirstArgumentIndentation:
-  Enabled: false
-
-Layout/ClosingParenthesisIndentation:
-  Enabled: false
-
-Layout/ArgumentAlignment:
-  Enabled: false
-

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at senid231@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,16 +0,0 @@
-source 'https://rubygems.org'
-gemspec
-
-gem 'activeadmin', ENV.fetch('ACTIVE_ADMIN_VERSION', '~> 3.2')
-gem 'rails', ENV.fetch('RAILS_VERSION', '~> 7.1.0')
-gem 'sprockets-rails'
-gem 'sassc-rails'
-
-group :test do
-  gem 'capybara'
-  gem 'cuprite'
-  gem 'puma'
-  gem 'rspec-rails', '~> 6.0'
-  gem 'simplecov', require: false
-  gem 'sqlite3', '~> 2.0'
-end

data/Rakefile

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: [:spec]

data/bin/console

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require 'bundler/setup'
-require 'capybara_active_admin'
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require 'irb'
-IRB.start(__FILE__)

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/capybara_active_admin.gemspec

@@ -1,33 +0,0 @@
-# frozen_string_literal: true
-
-require_relative 'lib/capybara/active_admin/version'
-
-Gem::Specification.new do |spec|
-  spec.name          = 'capybara_active_admin'
-  spec.version       = Capybara::ActiveAdmin::VERSION
-  spec.authors       = ['Denis Talakevich']
-  spec.email         = ['senid231@gmail.com']
-
-  spec.summary       = 'Capybara DSL for fast and easy testing Active Admin applications.'
-  spec.description   = 'Capybara DSL for fast and easy testing Active Admin applications.'
-  spec.homepage      = 'https://github.com/active_admin_plugins/capybara_active_admin'
-  spec.license       = 'MIT'
-  spec.required_ruby_version = Gem::Requirement.new('>= 3.3.0')
-
-  spec.metadata['homepage_uri'] = spec.homepage
-  spec.metadata['source_code_uri'] = spec.homepage
-  spec.metadata['changelog_uri'] = "#{spec.homepage}/blob/master/CHANGELOG.md"
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files = Dir.chdir(File.expand_path(__dir__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  end
-  spec.bindir        = 'exe'
-  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
-  spec.require_paths = ['lib']
-
-  spec.add_dependency 'activeadmin', '>= 3.0', '< 4.0'
-  # spec.add_dependency 'devise'
-  spec.add_dependency 'rspec', '~> 3.0'
-end

data/docs/.vuepress/config.js

@@ -1,12 +0,0 @@
-module.exports = {
-  title: 'Capybara Active Admin',
-  description: 'Capybara DSL for fast and easy testing Active Admin applications.',
-  base: '/capybara_active_admin/',
-  themeConfig: {
-    nav: [
-      { text: 'Guide', link: '/guide/' },
-      { text: 'API Reference', link: '/api/', target: '_blank' },
-      { text: 'GitHub', link: 'https://github.com/activeadmin-plugins/capybara_active_admin' }
-    ]
-  }
-}

data/docs/.vuepress/styles/index.styl

@@ -1,3 +0,0 @@
-div.theme-default-content:not(.custom) {
-  max-width: 75%;
-}

data/docs/README.md

@@ -1,41 +0,0 @@
----
-home: true
-actionText: Get Started →
-actionLink: /guide/
-footer: MIT Licensed | Copyright © 2020-present Denis Talakevich
----
-
-<div style="text-align: center">
-  <Bit/>
-</div>
-
-<div class="features">
-  <div class="feature">
-    <h2>Fast Test Writing</h2>
-    <p>Allow to focus on what you want to test instead of how to do it.</p>
-  </div>
-  <div class="feature">
-    <h2>Simplicity</h2>
-    <p>Following Ruby an Capybara naming conventions allows easily to read and understand tests code.</p>
-  </div>
-  <div class="feature">
-    <h2>Customizable</h2>
-    <p>You can easy extend, customize, and mix parts of library to fit your needs.</p>
-  </div>
-</div>
-
-### As Easy as 1, 2, 3
-
-```bash
-# install
-gem install capybara_active_admin
-# OR echo "gem 'capybara_active_admin', group: :test, require: false" >> Gemfile
-```
-```ruby
-# require in in rspec/rails_helper.rb
-require 'capybara/active_admin/rspec'
-```
-
-::: warning COMPATIBILITY NOTE
-requires Ruby >= 2.3.
-:::

data/docs/guide/README.md

@@ -1,113 +0,0 @@
-# Introduction
-
-<Bit/>
-
-`Capybara::ActiveAdmin` created to write tests as fast as `ActiveAdmin` resource which they are test.
-
-## Getting Started
-
-### Installation
- 
-```ruby
-# Gemfile
-
-gem 'capybara_active_admin', group: :test, require: false
-```
-
-```ruby
-# spec/rails_helper.rb
-
-# after require 'rspec' or 'rspec/rails'
-require 'capybara/active_admin/rspec'
-```
-
-### Usage
-
-For example we have such database table
-```ruby
-create_table :users do |t|
-  t.string :full_name
-  t.timestamps
-end
-```
-And such `ActiveRecord` model
-```ruby
-class User < ActiveRecord::Base
-  validates :full_name, presence: true
-end
-```
-And there is our `ActiveAdmin` resource
-```ruby
-ActiveAdmin.register User do
-  permit_params :full_name
-end
-```
-
-Our test can look like below
-```ruby
-# spec/system/users_spec.rb
-
-RSpec.describe 'Users' do
-
-  describe 'index page' do
-    subject do
-      visit admin_users_path
-    end
-
-    it 'have no table' do
-      subject
-
-      expect(page).to have_text('There are no Users yet.')
-      expect(page).to have_action_item('New User')
-      expect(page).to_not have_action_item('Edit User')
-      expect(page).to_not have_table
-    end
-
-    context 'with users' do
-      let!(:users) do
-        [
-          User.create!(full_name: 'John Doe'),
-          User.create!(full_name: 'Jane Air')
-        ]
-      end
-
-      it 'have correct table rows' do
-        subject
-
-        # you can check that table is visible on page
-        expect(page).to have_table
-
-        # checkout data within table,
-        # same as `within(table_selector) do`
-        within_table_for do
-          # check how many rows in table (tr)
-          expect(page).to have_table_row(count: 2)
-          # or cells (td)
-          expect(page).to have_table_cell(count: 10)
-          # or check cell of specific column contain specific value,
-          # accepts same options as `have_selector`, such as :text, :exact_text, :count, etc.
-          expect(page).to have_table_cell(text: 'John Doe', column: 'Full Name')
-
-          # we can check data inside specific row by record id,
-          # or we can find it by index in table `within_table_row(index: 0) do`.
-          within_table_row(id: users.first.id) do
-            # default columns for users table are id, full_name, created_at, updated_at, actions.
-            expect(page).to have_table_cell(count: 5)
-            expect(page).to have_table_cell(text: 'John Doe')
-            # or you can write
-            expect(page).to have_table_cell(text: 'John Doe', column: 'Full Name')
-            # negate matcher
-            expect(page).to_not have_table_cell(text: 'John Doe', column: 'Id')
-          end
-
-          within_table_row(id: users.second.id) do
-            expect(page).to have_table_cell(text: users.second.id, column: 'Id')
-            expect(page).to have_table_cell(text: 'Jane Air', column: 'Full Name')
-            expect(page).to_not have_table_cell(text: 'John Doe')
-          end
-        end
-      end
-    end
-  end
-end
-```

data/package.json

@@ -1,9 +0,0 @@
-{
-  "scripts": {
-    "docs:dev": "vuepress dev docs",
-    "docs:build": "vuepress build docs"
-  },
-  "devDependencies": {
-    "vuepress": "^1.4.1"
-  }
-}