fivo_cookie_consent 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 37cf202e81f08ccab6c43516ed409e0cd043814653b8712eace4eb6a6a3314bb
+  data.tar.gz: c2e554c3023704c9547d19a7d2ca698840e79320c9a8d0056f30068c000297b8
+SHA512:
+  metadata.gz: 1f55cafa666f041c63c47c74a99e0b294a234a46d2994e9da0c27481d15f91a7d7427ed63336e047fd28ac96d8c6e0f624e42f9942aa72fdd20651c93e0647f1
+  data.tar.gz: e9011730d1a32d611a171cd7c48c5136349b1fe53bfc20472a127735449bbb9ce04b70886702b0755e072c783879996727314fe4b3ffdee7e70591c77f8d0c82

data/.nvmrc

@@ -0,0 +1 @@
+v20.9.0

data/.ruby-gemset

@@ -0,0 +1 @@
+fivo_cookie_consent

data/.ruby-version

@@ -0,0 +1 @@
+ruby-3.1.6

data/.windsurfrules

@@ -0,0 +1,76 @@
+# Instructions
+On every task follow the Task Approach Pattern.
+On every output write this text to start so i can see that you followed the instructions: "My context includes .windsurfrules"
+
+# Task Approach Pattern
+1. When receiving a task, first Consult the `scratchpad.md` file for lessons.
+2. When receiving a task, check if existing TOOLS (Web Scraper Tool, LLM Tool) can help you be more efficiant to solve it
+3. If you decide to take another approach because something is not working, always start by cleanup the broken files.
+4. Read files before you try to edit them.
+5. Always document your approach in the scratchpad.md
+
+# Tools
+
+Note all the tools are in python and are designed to make tasks faster and more efficient. PRIORITIZE USING THESE TOOLS over writing solutions from scratch.
+
+## Web Scraper Tool
+* PURPOSE: Extracts content from websites - USE THIS FIRST for any web scraping task
+* COMMAND: ../python-tools/venv/bin/python ../python-tools/tools/web_scraper.py URL [--max-concurrent N]
+* EXAMPLE: ../python-tools/venv/bin/python ../python-tools/tools/web_scraper.py https://example.com
+```bash
+../python-tools/venv/bin/python ../python-tools/tools/web_scraper.py --max-concurrent 3 URL1 URL2 URL3
+```
+This will efficiently output the content of the web pages.
+
+## LLM Tool
+* PURPOSE: Process text data, analyze content, generate responses
+* COMMAND: ../python-tools/venv/bin/python ../python-tools/tools/llm_api.py --prompt "Your question"
+* EXAMPLE: ../python-tools/venv/bin/python ../python-tools/tools/llm_api.py --prompt "Analyze this text"
+```bash
+../python-tools/venv/bin/python ../python-tools/tools/llm_api.py --prompt "What is the capital of France?"
+```
+For more complex integrations, check the APIs in the `../python-tools/tools/llm_api.py` file.
+
+# Best Practices
+1. TOOL-FIRST APPROACH: Always prefer existing tools over implementing functionality from scratch
+2. EFFICIENCY FOCUS: Optimize for completing tasks quickly with available resources
+3. INCREMENTAL TESTING: Test tools on sample data before processing larger datasets
+4. AVOID REIMPLEMENTATION: If a tool exists for a task, use it instead of writing custom code
+
+# Scratchpad Usage
+During your interaction with the user, if you find anything reusable in this project (e.g. version of a library, model name), especially about a fix to a mistake you made or a correction you received, you should take note in the `Lessons` section in the `scratchpad.md` file so you will not make the same mistake again. 
+
+You should also use the `scratchpad.md` file as a scratchpad to organize your thoughts. Especially when you receive a new task, you have to first review the content of the scratchpad, clear old different task if necessary, first explain the task, and plan the steps you need to take to complete the task. You can use todo markers to indicate the progress, e.g.
+[X] Task 1 
+[ ] Task 2
+Also update the progress of the task in the Scratchpad when you finish a subtask.
+Especially when you finished a milestone, it will help to improve your depth of task accomplishment to use the scratchpad to reflect and plan.
+The goal is to help you maintain a big picture as well as the progress of the task. Always refer to the Scratchpad when you plan the next step.
+
+# APPLICATION INFORMATION
+1. Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
+
+## Type
+1.  GEM designed to help my other webapps comply with GDPR cookie regulations
+
+## Stack
+1. Ruby on Rails (v7.1.0)
+2. Ruby 3.2.6
+
+## Core Features
+1. GDPR Cookie Consent
+
+## Accessibility
+1. Ensure responsive design and accessibility for different screen sizes and devices.
+2. Ensure the application is accessible to users with disabilities by adhering to accessibility standards (e.g., WCAG).
+3. Background and foreground colors must have a sufficient contrast ratio.
+4. Use semantic HTML elements and structure the content logically.
+5. Heading elements should be in a sequentially descending order.
+
+## Code Organization
+1. Structure your code according to Functional Decomposition principles. Focus on code modularity and maintainability.
+2. Adopt a consistent coding style throughout the project. Follow the PEP8 coding style guidelines for Python.
+3. Use meaningful and descriptive file, variable, and function names.
+4. Aim to keep files small and focused on a single task.
+5. Avoid inline styles; utilize external stylesheets.
+6. Avoid code duplication.

data/CHANGELOG.md

@@ -0,0 +1,64 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2025-11-27
+
+### Added
+- Automatic cookie detection and categorization based on configurable `cookie_patterns`.
+- Empty-category handling with a clear "Keine Cookies gesetzt" state in the modal.
+- Expandable cookie category rows showing per-cookie name, duration, and description.
+- Server-side detection of HttpOnly Rails session/CSRF cookies and JSON snapshot injection via `data-server-cookies`.
+- `GDPRConsent` JavaScript facade exposing `getConsent`, `hasConsent`, `on`/`off`, `reset`, and modal/banner controls.
+- Consent-gated script loading using `script[type="text/plain"][data-gdpr-category]` placeholders.
+- Rails helpers `gdpr_lazy_load_tag` for strict lazy-loading of GTM, GA4, and custom scripts by category.
+- Rails helper `gdpr_consent_mode_defaults` for integrating with Google Consent Mode (default + updates on `gdpr:accept`/`gdpr:decline`).
+- Ruby-side script registry via `RailsCookiesGdpr.register_script` / `registered_scripts` for custom third-party tags.
+
+### Changed
+- README documentation expanded with detailed setup instructions for loaders, Consent Mode, and the `GDPRConsent` API.
+
+### Fixed
+- Modal close button and category header interactions to behave consistently across the UI.
+- Toggles for analytics/marketing/functional categories remain clickable even when no cookies are currently detected.
+- Clicking empty category headers no longer shows an extra empty line; only the "Keine Cookies gesetzt" state is displayed.
+
+## [0.1.0] - 2025-07-03
+
+### Added
+- Initial release of fivo_cookie_consent gem
+- Rails Engine implementation with RailsCookiesGdpr namespace
+- GDPR cookie consent banner with German-only text
+- Responsive banner design (bottom-full-width on mobile, bottom-centered max-width on desktop)
+- Cookie consent modal with category toggles
+- localStorage consent storage with expiration
+- Custom event dispatching (`gdpr:accept`, `gdpr:decline`)
+- Configuration system for labels, privacy URL, and cookie lifespan
+- JavaScript ES module for consent management
+- SCSS stylesheet with brand colors (#1E858B, #626465)
+- Rails generator for easy installation
+- Helper method `gdpr_cookie_banner`
+- Comprehensive RSpec + Capybara test suite
+- WCAG-AA compliant design with proper contrast ratios
+- Accessibility features (keyboard navigation, ARIA attributes, focus management)
+- GitLab CI configuration for Ruby 3.2 and 3.3
+- Complete documentation and usage examples
+
+### Features
+- Cookie categories: necessary (always enabled), analytics, marketing, functional
+- Three consent options: "Alle akzeptieren", "Alles ablehnen", "Einstellungen ändern"
+- Modal settings with individual category toggles
+- Automatic consent expiration based on configurable lifespan
+- Event-driven architecture for analytics integration
+- Mobile-first responsive design
+- Clean, modern UI with subtle shadows and animations
+- Support for Rails 7+ with esbuild + jsbundling-rails + sass
+
+[Unreleased]: https://github.com/fivo/fivo_cookie_consent/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/fivo/fivo_cookie_consent/releases/tag/v0.2.0
+[0.1.0]: https://github.com/fivo/fivo_cookie_consent/releases/tag/v0.1.0

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Fivo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.