activeadmin_favorites 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 51027c5b7293ba07e01be5677e4785b9d682c177ef6cea6137b4f658cb2ede71
-  data.tar.gz: 24bbfd1df143374ccd612f14e6bec75967a44571ad58013d1203ca03c44c02be
+  metadata.gz: 9c52fa8f127b186b02bab3ea8dbb27534a1cec621540c9e7856795f7d4353226
+  data.tar.gz: 3cd3a3248cd4c416229b1dfc6051fc478de502ad1366a6c8342a1c40cfa7a2bb
 SHA512:
-  metadata.gz: e62dc3e8a67dcf78d388d00764eef5f9e4051d7ae446680d5c28775eebd6b3efb5c09443b19a0cf64e2333bdb4acfe03fbae62cc6021ec4b84d19287b1cb11ea
-  data.tar.gz: 51fad41e3d2841c6d4d55758e33e62e74539c96dc27035dcac0ddf5de2568a197da9b921aee3f90467e2233ca4554adc23659765acb166a9d3696130c11a1785
+  metadata.gz: 63de9c366a211be6786a74d5dc3716e1873bff84ecdeaae074c6247cc3414597750a4aaf5031e4bee55e7d86522c24a73313739382ecdabe1e190e1aaff49a71
+  data.tar.gz: 24c4a24fd86f690651b9b3c608c381ca2f32221d4e3852380a94d97ffa3bef7403dd6c04c1feb1de66d8c1591e2b29e6e9557d31e09165611529f22806b0ed1d

data/CHANGELOG.md

@@ -1,8 +1,10 @@
 # CHANGELOG
 
-## Unreleased
+## 0.1.1 (2026-09-07)
 
-- CI: run Rails 7.2 appraisal on Ruby 3.4; refresh lockfiles for current advisories (`loofah` 2.25.2, `rails-html-sanitizer` 1.7.1) and development gems (`rbs` ~> 4).
+- Keep favorites registration working after ActiveAdmin reload when a custom page is already registered.
+- Keep JSON and CSV collection downloads working on ActiveAdmin resources that only expose the index action.
+- CI: run Rails 7.2 appraisal on Ruby 3.4; refresh lockfiles for current advisories (`loofah` 2.25.2, `rails-html-sanitizer` 1.7.1, `json` 2.21.2, `sqlite3` 2.9.6) and development gems (`rbs` ~> 4).
 
 ## 0.1.0 (2026-07-13)
 

data/CODE_OF_CONDUCT.md

@@ -1,31 +1,26 @@
 # Code of Conduct
 
-## Our pledge
+## Pledge
 
-We pledge to make participation in our community a harassment-free experience for everyone. We operate on principles of mutual respect, privacy, and authentic engagement. We value substantive contributions and clarity on intentions.
+Participation is a harassment-free experience. Treat each other with respect. Keep private context private.
 
-## Our standards
+## Expected behavior
 
-Examples of behavior that contributes to a positive environment include:
+- Engage with genuine curiosity. Admit uncertainty.
+- Own every line you submit, including generated code.
+- Correct errors politely.
+- Use language that welcomes people and respects identity and privacy.
 
-- Authenticity: engaging with genuine curiosity and admitting uncertainty rather than feigning knowledge.
-- Responsible innovation: taking full responsibility for any content or code contributed, whether manually written or generated by automation tools.
-- Gentle correction: responding politely to errors. We view mistakes as opportunities for learning, provided they are addressed with humility.
-- Inclusive language: using language that welcomes diverse perspectives and respects the privacy and identity of all participants.
+## Unacceptable behavior
 
-Examples of unacceptable behavior include:
+- Harassment, trolling, or insulting comments, public or private.
+- Using jargon or volume, including automated spam, to silence others.
+- Sharing others' data or personal context without permission.
 
-- Harassment: public or private harassment, trolling, or insulting comments.
-- Weaponized complexity: using jargon or overwhelming volume (including automated spam) to silence others.
-- Publishing private information: sharing others' data or personal context without explicit permission.
+## Automation
 
-## Artificial intelligence and automation
-
-In accordance with our commitment to collective awareness:
-
-- Contributors are responsible for the accuracy and security of any AI-generated artifacts they submit.
-- "The AI wrote it" is not a valid excuse for introducing bugs, security vulnerabilities, or bias.
+You remain responsible for bugs, security holes, and bias in generated artifacts you submit.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@kiskolabs.com. All complaints will be reviewed and investigated promptly and fairly.
+Report abusive or harassing behavior to contact@kiskolabs.com. Reports are reviewed and investigated.

data/CONTRIBUTING.md

@@ -1,29 +1,23 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to activeadmin_favorites. We value learning over perfection but require rigor and responsibility.
+## Automation authorship
 
-## The golden rule of automation
+You may use AI and automation tools. You remain the author of every line you submit: review, debug, and understand the change.
 
-We welcome the use of AI and automation tools to reduce toil, but you must strictly adhere to the following:
+Keep pull requests small enough to review. Annotate non-obvious logic.
 
-1. You are the author. You act as the responsible agent for any code you submit. You must review, debug, and understand every line.
-2. Manage cognitive load. Do not submit massive, unreviewed automated dumps. Respect the reviewers' time by annotating complex logic.
-3. Security. Never feed project secrets or private context into public AI models.
+Never send project secrets or private context to public models.
 
 ## How to contribute
 
 ### Reporting issues
 
-- Verify accuracy before posting. Avoid generalizations.
-- Use issue templates to provide clear goals, constraints, and reproduction steps.
+Verify the facts before filing. Use issue templates for goals, constraints, and reproduction steps.
 
-### Pull request process
+### Pull requests
 
-- Scope: keep PRs focused on a single goal.
-- Context: explain why the change is necessary.
-- Testing: run `make test` locally before opening a PR.
+Keep one pull request to one goal. Explain why the change is needed. Run smoke tests and regression checks locally before opening the request.
 
-### Review process
+### Review
 
-- We encourage productive friction. Expect questions about your approach.
-- If a reviewer suggests a change, view it as mutual aid, not criticism.
+Reviewers will ask about approach and trade-offs. Treat suggested changes as part of the work.

data/GOVERNANCE.md

@@ -1,29 +1,25 @@
 # Project Governance
 
-## Overview
-
-This project balances individual autonomy with collective coordination. We aim for a workflow that supports rapid iteration while maintaining strict guardrails for safety and architectural integrity.
-
 ## Roles
 
 ### Contributors
 
-Anyone who submits code, documentation, or participates in discussions. Contributors are expected to exercise direct action—taking ownership of problems they identify—while adhering to our quality standards.
+Anyone who submits code, documentation, or participates in discussions. Contributors take ownership of problems they identify and follow the project's quality standards.
 
-### Maintainers (Human Oversight)
+### Maintainers
 
-Maintainers are responsible for:
+Maintainers:
 
-1. Strategic judgment: defining scope and architectural direction.
-2. Review: verifying that contributions (human or automated) meet security and logic standards.
-3. Consensus building: facilitating decisions when the community is divided.
+1. Set scope and architectural direction.
+2. Review contributions (human or automated) against security and logic standards.
+3. Decide when the community is divided.
 
-## Decision making process
+## Decision making
 
 ### Lazy consensus
 
-For most routine changes, we operate on lazy consensus. If a proposal is made and no objections are raised within two weeks, it is considered approved.
+For routine changes, a proposal that draws no objection within two weeks is approved.
 
-### Strategic alignment
+### Maintainer approval
 
-Major architectural changes, high-risk automation integrations, or changes that affect business logic require explicit approval from the maintainers. We prioritize substance over performance—a change must solve a real problem, not just appear polished.
+Major architectural changes, high-risk automation integrations, or changes that affect business logic need explicit maintainer approval. A change must solve a real problem.

data/SECURITY.md

@@ -1,27 +1,25 @@
 # SECURITY
 
-## Reporting a vulnerability
-
-Do NOT open a public GitHub issue for security vulnerabilities.
+## Reporting a Vulnerability
 
 Email security details to: security@kiskolabs.com
 
-Include: description, steps to reproduce, potential impact, and suggested fix (if available).
+Send the report only to that address. Include description, steps to reproduce, potential impact, and a suggested fix when you have one.
 
-### Response timeline
+### Response Timeline
 
-- We will acknowledge receipt of your report
-- We will provide an initial assessment
-- We will keep you informed of our progress and resolution timeline
+- We will acknowledge receipt of your report.
+- We will provide an initial assessment.
+- We will keep you informed of our progress and resolution timeline.
 
-### Disclosure policy
+### Disclosure Policy
 
-- We will work with you to understand and resolve the issue
-- We will credit you for the discovery (unless you prefer to remain anonymous)
-- We will publish a security advisory after the vulnerability is patched
-- We will coordinate public disclosure with you
+- We will work with you to understand and resolve the issue.
+- We will credit you for the discovery unless you prefer to remain anonymous.
+- We will publish a security advisory after the vulnerability is patched.
+- We will coordinate public disclosure with you.
 
-## Automation security
+## Automation Security
 
-- Context isolation: it is strictly forbidden to include production credentials, API keys, or personally identifiable information in prompts sent to third-party LLMs or automation services.
-- Supply chain: all automated dependencies must be verified.
+- Keep production credentials, API keys, and personal data out of prompts sent to third-party models or automation services.
+- Verify automated dependencies.

data/activeadmin_favorites.gemspec

@@ -55,7 +55,7 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "rake", "~> 13"
   spec.add_development_dependency "rspec", "~> 3"
   spec.add_development_dependency "rspec-rails", ">= 6"
-  spec.add_development_dependency "sqlite3", ">= 1"
+  spec.add_development_dependency "sqlite3", ">= 2.9.6"
   spec.add_development_dependency "rubocop-rails", "~> 2.34"
   spec.add_development_dependency "rubocop-rspec", "~> 3.8"
   spec.add_development_dependency "rubocop-thread_safety", "~> 0.7"

data/lib/activeadmin/favorites/install.rb

@@ -17,7 +17,7 @@ module ActiveAdmin
 
       def configure_favorites_resource!
         resource = ActiveAdmin.application.namespace(ActiveAdmin::Favorites.config.namespace_name)
-          .resources.find { |config| config.resource_class == Favorite }
+          .resources.find { |config| config.is_a?(ActiveAdmin::Resource) && config.resource_class == Favorite }
         return unless resource
 
         resource.instance_variable_set(:@batch_actions, {}) if resource.instance_variable_get(:@batch_actions).nil?

data/lib/activeadmin/favorites/register_favorites.rb

@@ -265,7 +265,7 @@ module ActiveAdmin
 
       def resource_registered?
         ActiveAdmin.application.namespace(ActiveAdmin::Favorites.config.namespace_name)
-          .resources.any? { |resource| resource.resource_class == Favorite }
+          .resources.any? { |resource| resource.is_a?(ActiveAdmin::Resource) && resource.resource_class == Favorite }
       end
     end
   end

data/lib/activeadmin/favorites/version.rb

@@ -2,6 +2,6 @@
 
 module ActiveAdmin
   module Favorites
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

data/lib/activeadmin/favorites/view_lens/resource_dsl.rb

@@ -7,8 +7,8 @@ module ActiveAdmin
         extend ActiveSupport::Concern
 
         included do
-          before_action :apply_active_admin_favorites_lens, only: [:index, :show]
-          after_action :clear_active_admin_favorites_lens, only: [:index, :show]
+          before_action :apply_active_admin_favorites_lens, if: -> { %w[index show].include?(action_name) }
+          after_action :clear_active_admin_favorites_lens, if: -> { %w[index show].include?(action_name) }
 
           helper_method :active_admin_favorites_catalog, :active_admin_favorites_layout
         end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: activeadmin_favorites
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Andrei Makarov
@@ -189,14 +189,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '1'
+        version: 2.9.6
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '1'
+        version: 2.9.6
 - !ruby/object:Gem::Dependency
   name: rubocop-rails
   requirement: !ruby/object:Gem::Requirement