data_porter 0.1.0 → 0.4.0

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: data_porter
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.4.0
 platform: ruby
 authors:
 - Seryl Lounis
@@ -10,217 +10,153 @@ cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: csv
+  name: creek
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '2.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '2.6'
 - !ruby/object:Gem::Dependency
-  name: phlex
+  name: csv
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '3.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '3.0'
 - !ruby/object:Gem::Dependency
-  name: rails
+  name: phlex
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '2.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '2.0'
 - !ruby/object:Gem::Dependency
-  name: store_model
+  name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '7.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '9.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '7.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '9.0'
 - !ruby/object:Gem::Dependency
-  name: turbo-rails
+  name: store_model
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '4.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '4.0'
 description: 'A mountable Rails engine providing a complete data import workflow:
-  upload/configure, preview with validation, and import. Supports CSV, JSON, and API
-  sources with a simple DSL for defining import targets.'
+  upload/configure, preview with validation, and import. Supports CSV, JSON, XLSX,
+  and API sources with a simple DSL for defining import targets.'
 email:
 - seryllounis@outlook.fr
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".claude/commands/blog-status.md"
-- ".claude/commands/blog.md"
-- ".claude/commands/task-done.md"
-- ".claude/commands/tm/add-dependency.md"
-- ".claude/commands/tm/add-subtask.md"
-- ".claude/commands/tm/add-task.md"
-- ".claude/commands/tm/analyze-complexity.md"
-- ".claude/commands/tm/analyze-project.md"
-- ".claude/commands/tm/auto-implement-tasks.md"
-- ".claude/commands/tm/command-pipeline.md"
-- ".claude/commands/tm/complexity-report.md"
-- ".claude/commands/tm/convert-task-to-subtask.md"
-- ".claude/commands/tm/expand-all-tasks.md"
-- ".claude/commands/tm/expand-task.md"
-- ".claude/commands/tm/fix-dependencies.md"
-- ".claude/commands/tm/help.md"
-- ".claude/commands/tm/init-project-quick.md"
-- ".claude/commands/tm/init-project.md"
-- ".claude/commands/tm/install-taskmaster.md"
-- ".claude/commands/tm/learn.md"
-- ".claude/commands/tm/list-tasks-by-status.md"
-- ".claude/commands/tm/list-tasks-with-subtasks.md"
-- ".claude/commands/tm/list-tasks.md"
-- ".claude/commands/tm/next-task.md"
-- ".claude/commands/tm/parse-prd-with-research.md"
-- ".claude/commands/tm/parse-prd.md"
-- ".claude/commands/tm/project-status.md"
-- ".claude/commands/tm/quick-install-taskmaster.md"
-- ".claude/commands/tm/remove-all-subtasks.md"
-- ".claude/commands/tm/remove-dependency.md"
-- ".claude/commands/tm/remove-subtask.md"
-- ".claude/commands/tm/remove-subtasks.md"
-- ".claude/commands/tm/remove-task.md"
-- ".claude/commands/tm/setup-models.md"
-- ".claude/commands/tm/show-task.md"
-- ".claude/commands/tm/smart-workflow.md"
-- ".claude/commands/tm/sync-readme.md"
-- ".claude/commands/tm/tm-main.md"
-- ".claude/commands/tm/to-cancelled.md"
-- ".claude/commands/tm/to-deferred.md"
-- ".claude/commands/tm/to-done.md"
-- ".claude/commands/tm/to-in-progress.md"
-- ".claude/commands/tm/to-pending.md"
-- ".claude/commands/tm/to-review.md"
-- ".claude/commands/tm/update-single-task.md"
-- ".claude/commands/tm/update-task.md"
-- ".claude/commands/tm/update-tasks-from-id.md"
-- ".claude/commands/tm/validate-dependencies.md"
-- ".claude/commands/tm/view-models.md"
-- ".env.example"
-- ".mcp.json"
-- ".taskmaster/CLAUDE.md"
-- ".taskmaster/config.json"
-- ".taskmaster/docs/prd.txt"
-- ".taskmaster/state.json"
-- ".taskmaster/tasks/task_001.md"
-- ".taskmaster/tasks/task_002.md"
-- ".taskmaster/tasks/task_003.md"
-- ".taskmaster/tasks/task_004.md"
-- ".taskmaster/tasks/task_005.md"
-- ".taskmaster/tasks/task_006.md"
-- ".taskmaster/tasks/task_007.md"
-- ".taskmaster/tasks/task_008.md"
-- ".taskmaster/tasks/task_009.md"
-- ".taskmaster/tasks/task_010.md"
-- ".taskmaster/tasks/task_011.md"
-- ".taskmaster/tasks/task_012.md"
-- ".taskmaster/tasks/task_013.md"
-- ".taskmaster/tasks/task_014.md"
-- ".taskmaster/tasks/task_015.md"
-- ".taskmaster/tasks/task_016.md"
-- ".taskmaster/tasks/task_017.md"
-- ".taskmaster/tasks/task_018.md"
-- ".taskmaster/tasks/task_019.md"
-- ".taskmaster/tasks/task_020.md"
-- ".taskmaster/tasks/tasks.json"
-- ".taskmaster/templates/example_prd.txt"
-- ".taskmaster/templates/example_prd_rpg.txt"
 - CHANGELOG.md
-- CLAUDE.md
 - CODE_OF_CONDUCT.md
 - CONTRIBUTING.md
 - LICENSE
 - README.md
+- ROADMAP.md
 - Rakefile
+- app/assets/javascripts/data_porter/stimulus.min.js
+- app/assets/javascripts/data_porter/turbo.min.js
+- app/assets/stylesheets/data_porter/alerts.css
 - app/assets/stylesheets/data_porter/application.css
+- app/assets/stylesheets/data_porter/badges.css
+- app/assets/stylesheets/data_porter/base.css
+- app/assets/stylesheets/data_porter/cards.css
+- app/assets/stylesheets/data_porter/layout.css
+- app/assets/stylesheets/data_porter/mapping.css
+- app/assets/stylesheets/data_porter/modal.css
+- app/assets/stylesheets/data_porter/preview.css
+- app/assets/stylesheets/data_porter/progress.css
+- app/assets/stylesheets/data_porter/table.css
 - app/channels/data_porter/import_channel.rb
 - app/controllers/data_porter/imports_controller.rb
+- app/controllers/data_porter/mapping_templates_controller.rb
+- app/javascript/data_porter/mapping_controller.js
 - app/javascript/data_porter/progress_controller.js
+- app/javascript/data_porter/template_form_controller.js
 - app/jobs/data_porter/dry_run_job.rb
+- app/jobs/data_porter/extract_headers_job.rb
 - app/jobs/data_porter/import_job.rb
 - app/jobs/data_porter/parse_job.rb
 - app/models/data_porter/data_import.rb
+- app/models/data_porter/mapping_template.rb
 - app/views/data_porter/imports/index.html.erb
 - app/views/data_porter/imports/new.html.erb
 - app/views/data_porter/imports/show.html.erb
-- config/database.yml
+- app/views/data_porter/mapping_templates/_form.html.erb
+- app/views/data_porter/mapping_templates/edit.html.erb
+- app/views/data_porter/mapping_templates/index.html.erb
+- app/views/data_porter/mapping_templates/new.html.erb
+- app/views/layouts/data_porter/application.html.erb
 - config/routes.rb
-- docs/SPEC.md
-- docs/UI.md
-- docs/blog/001-why-build-a-data-import-engine.md
-- docs/blog/002-scaffolding-a-rails-engine.md
-- docs/blog/003-configuration-dsl.md
-- docs/blog/004-store-model-jsonb.md
-- docs/blog/005-target-dsl.md
-- docs/blog/006-parsing-csv-sources.md
-- docs/blog/007-orchestrator.md
-- docs/blog/008-actioncable-stimulus.md
-- docs/blog/009-phlex-ui-components.md
-- docs/blog/010-controllers-routing.md
-- docs/blog/011-generators.md
-- docs/blog/012-json-api-sources.md
-- docs/blog/013-testing-rails-engine.md
-- docs/blog/014-dry-run.md
-- docs/blog/015-publishing-retro.md
-- docs/blog/016-erb-view-templates.md
-- docs/blog/017-showcase-final-retro.md
-- docs/blog/BACKLOG.md
-- docs/blog/SERIES.md
+- docs/CONFIGURATION.md
+- docs/MAPPING.md
+- docs/SOURCES.md
+- docs/TARGETS.md
 - docs/screenshots/index-with-previewing.jpg
 - docs/screenshots/index.jpg
+- docs/screenshots/mapping.jpg
 - docs/screenshots/modal-new-import.jpg
 - docs/screenshots/preview.jpg
 - lib/data_porter.rb
 - lib/data_porter/broadcaster.rb
 - lib/data_porter/components.rb
 - lib/data_porter/components/base.rb
-- lib/data_porter/components/failure_alert.rb
-- lib/data_porter/components/preview_table.rb
-- lib/data_porter/components/progress_bar.rb
-- lib/data_porter/components/results_summary.rb
-- lib/data_porter/components/status_badge.rb
-- lib/data_porter/components/summary_cards.rb
+- lib/data_porter/components/mapping/column_row.rb
+- lib/data_porter/components/mapping/form.rb
+- lib/data_porter/components/mapping/template_select.rb
+- lib/data_porter/components/preview/results_summary.rb
+- lib/data_porter/components/preview/summary_cards.rb
+- lib/data_porter/components/preview/table.rb
+- lib/data_porter/components/progress/bar.rb
+- lib/data_porter/components/shared/failure_alert.rb
+- lib/data_porter/components/shared/status_badge.rb
 - lib/data_porter/configuration.rb
 - lib/data_porter/dsl/api_config.rb
 - lib/data_porter/dsl/column.rb
@@ -233,6 +169,7 @@ files:
 - lib/data_porter/sources/base.rb
 - lib/data_porter/sources/csv.rb
 - lib/data_porter/sources/json.rb
+- lib/data_porter/sources/xlsx.rb
 - lib/data_porter/store_models/error.rb
 - lib/data_porter/store_models/import_record.rb
 - lib/data_porter/store_models/report.rb
@@ -241,6 +178,7 @@ files:
 - lib/data_porter/version.rb
 - lib/generators/data_porter/install/install_generator.rb
 - lib/generators/data_porter/install/templates/create_data_porter_imports.rb.erb
+- lib/generators/data_porter/install/templates/create_data_porter_mapping_templates.rb.erb
 - lib/generators/data_porter/install/templates/initializer.rb
 - lib/generators/data_porter/target/target_generator.rb
 - lib/generators/data_porter/target/templates/target.rb.tt
@@ -249,9 +187,8 @@ homepage: https://github.com/SerylLns/data_porter
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://github.com/SerylLns/data_porter
   source_code_uri: https://github.com/SerylLns/data_porter
-  changelog_uri: https://github.com/SerylLns/data_porter/blob/master/CHANGELOG.md
+  changelog_uri: https://github.com/SerylLns/data_porter/blob/main/CHANGELOG.md
   rubygems_mcp_server_uri: https://rubygems.org/gems/data_porter
   rubygems_mfa_required: 'true'
 rdoc_options: []

data/.claude/commands/blog-status.md

@@ -1,10 +0,0 @@
-Show the status of the DataPorter blog article series.
-
-1. List all existing articles in `docs/blog/` with their title, part number, and published status
-2. Check `task-master list` for completed tasks since the last article
-3. Suggest 2-3 potential next article topics based on:
-   - Recently completed tasks not yet covered
-   - The natural progression of the series
-   - Topics that would be interesting for the Ruby/Rails community
-
-Format the output as a clear dashboard.

data/.claude/commands/blog.md

@@ -1,109 +0,0 @@
-Write the next blog article for the DataPorter series.
-
-Topic/title hint: $ARGUMENTS
-
-## Process
-
-1. **Read the series plan** at `docs/blog/SERIES.md` to identify which part this is and what it should cover.
-
-2. **Gather context:**
-   - `task-master list` to see completed tasks
-   - `git log --oneline -20` for recent commits
-   - Read the source files listed in the series plan for this part
-   - Read any previous articles in `docs/blog/` to maintain continuity
-
-3. **Write the article** in `docs/blog/NNN-slug.md` (NNN = part number, zero-padded).
-
-4. **Mandatory article structure:**
-
-```markdown
----
-title: "Building DataPorter #N — <Title>"
-series: "Building DataPorter - A Data Import Engine for Rails"
-part: N
-tags: [ruby, rails, rails-engine, gem-development, <2-3 topic tags>]
-published: false
----
-
-# <Title>
-
-> One-line summary of what the reader will learn.
-
-## Context
-
-Where we are in the series (1-2 sentences). Link to previous article.
-What we'll build in this article (clear scope).
-
-## The problem
-
-Why do we need this? Real-world scenario. Keep it short (3-5 sentences).
-
-## What we're building
-
-Show the end result first: a code snippet, a diagram, or a usage example.
-The reader should immediately understand where we're going.
-
-## Implementation
-
-### Step 1 — <Name>
-
-Explain the WHY, then show the code.
-
-\`\`\`ruby
-# path/to/file.rb
-<focused snippet, not full file>
-\`\`\`
-
-Brief explanation of what this does and why we chose this approach.
-
-### Step 2 — <Name>
-
-(repeat pattern: WHY -> code -> explain)
-
-### Step 3 — <Name>
-
-(repeat)
-
-## Decisions & tradeoffs
-
-| Decision | We chose | Over | Because |
-|----------|----------|------|---------|
-| ... | ... | ... | ... |
-
-## Testing it
-
-Show how to verify this works (spec snippet or console output).
-
-\`\`\`ruby
-# spec/...
-\`\`\`
-
-## Recap
-
-3-4 bullet points: what we built, what we learned.
-
-## Next up
-
-One paragraph teasing the next article in the series. End with a hook.
-
----
-
-*This is part N of the series "Building DataPorter". [Previous: ...](#) | [Next: ...](#)*
-*Code: [GitHub repo link]*
-```
-
-5. **Writing rules:**
-   - 5-8 minute read (~1000-1500 words)
-   - Max 3-4 implementation steps per article
-   - Code snippets: focused, 5-25 lines each (never full file dumps)
-   - Every snippet has a file path comment on line 1
-   - Explain decisions as "We chose X over Y because Z"
-   - Use the actual code from the codebase (not made-up examples)
-   - Conversational but technical tone: "Let's...", "Here's why..."
-   - English only
-   - No emojis in prose (OK in front matter tags)
-
-6. **After writing:**
-   - Update the article status in `docs/blog/SERIES.md` to `draft`
-   - Show: title, word count, reading time, and the decisions table
-   - Suggest 2-3 improvements or missing points

data/.claude/commands/task-done.md

@@ -1,27 +0,0 @@
-Mark a Taskmaster task as done and check if a blog article should be generated.
-
-Task ID: $ARGUMENTS
-
-## Process
-
-1. **Complete the task:**
-   ```
-   task-master set-status --id=$ARGUMENTS --status=done
-   ```
-
-2. **Check blog series:** Read `docs/blog/SERIES.md` and find which blog part includes this task.
-
-3. **Check if all tasks for that part are done:**
-   - Run `task-master show <id>` for each task in the blog part
-   - If ALL tasks for the part have status `done`, proceed to step 4
-   - If some tasks are still pending/in-progress, report progress ("Part N: 2/3 tasks done")
-
-4. **If part is ready, generate the article:**
-   - Follow the `/blog` command process
-   - Write the draft in `docs/blog/NNN-slug.md`
-   - Update SERIES.md status to `draft`
-
-5. **Show summary:**
-   - Task completed
-   - Blog part progress (e.g., "Part 5: 2/2 tasks done — article draft generated")
-   - Next task suggestion via `task-master next`

data/.claude/commands/tm/add-dependency.md

@@ -1,58 +0,0 @@
-Add Dependency
-
-Arguments: $ARGUMENTS
-Add a dependency between tasks.
-
-Arguments: $ARGUMENTS
-
-Parse the task IDs to establish dependency relationship.
-
-## Adding Dependencies
-
-Creates a dependency where one task must be completed before another can start.
-
-## Argument Parsing
-
-Parse natural language or IDs:
-- "make 5 depend on 3" → task 5 depends on task 3
-- "5 needs 3" → task 5 depends on task 3
-- "5 3" → task 5 depends on task 3
-- "5 after 3" → task 5 depends on task 3
-
-## Execution
-
-```bash
-task-master add-dependency --id=<task-id> --depends-on=<dependency-id>
-```
-
-## Validation
-
-Before adding:
-1. **Verify both tasks exist**
-2. **Check for circular dependencies**
-3. **Ensure dependency makes logical sense**
-4. **Warn if creating complex chains**
-
-## Smart Features
-
-- Detect if dependency already exists
-- Suggest related dependencies
-- Show impact on task flow
-- Update task priorities if needed
-
-## Post-Addition
-
-After adding dependency:
-1. Show updated dependency graph
-2. Identify any newly blocked tasks
-3. Suggest task order changes
-4. Update project timeline
-
-## Example Flows
-
-```
-/taskmaster:add-dependency 5 needs 3
-→ Task #5 now depends on Task #3
-→ Task #5 is now blocked until #3 completes
-→ Suggested: Also consider if #5 needs #4
-```

data/.claude/commands/tm/add-subtask.md

@@ -1,79 +0,0 @@
-Add Subtask
-
-Arguments: $ARGUMENTS
-Add a subtask to a parent task.
-
-Arguments: $ARGUMENTS
-
-Parse arguments to create a new subtask or convert existing task.
-
-## Adding Subtasks
-
-Creates subtasks to break down complex parent tasks into manageable pieces.
-
-## Argument Parsing
-
-Flexible natural language:
-- "add subtask to 5: implement login form"
-- "break down 5 with: setup, implement, test"
-- "subtask for 5: handle edge cases"
-- "5: validate user input" → adds subtask to task 5
-
-## Execution Modes
-
-### 1. Create New Subtask
-```bash
-task-master add-subtask --parent=<id> --title="<title>" --description="<desc>"
-```
-
-### 2. Convert Existing Task
-```bash
-task-master add-subtask --parent=<id> --task-id=<existing-id>
-```
-
-## Smart Features
-
-1. **Automatic Subtask Generation**
-   - If title contains "and" or commas, create multiple
-   - Suggest common subtask patterns
-   - Inherit parent's context
-
-2. **Intelligent Defaults**
-   - Priority based on parent
-   - Appropriate time estimates
-   - Logical dependencies between subtasks
-
-3. **Validation**
-   - Check parent task complexity
-   - Warn if too many subtasks
-   - Ensure subtask makes sense
-
-## Creation Process
-
-1. Parse parent task context
-2. Generate subtask with ID like "5.1"
-3. Set appropriate defaults
-4. Link to parent task
-5. Update parent's time estimate
-
-## Example Flows
-
-```
-/taskmaster:add-subtask to 5: implement user authentication
-→ Created subtask #5.1: "implement user authentication"
-→ Parent task #5 now has 1 subtask
-→ Suggested next subtasks: tests, documentation
-
-/taskmaster:add-subtask 5: setup, implement, test
-→ Created 3 subtasks:
-  #5.1: setup
-  #5.2: implement
-  #5.3: test
-```
-
-## Post-Creation
-
-- Show updated task hierarchy
-- Suggest logical next subtasks
-- Update complexity estimates
-- Recommend subtask order

data/.claude/commands/tm/add-task.md

@@ -1,81 +0,0 @@
-Add Task
-
-Arguments: $ARGUMENTS
-Add new tasks with intelligent parsing and context awareness.
-
-Arguments: $ARGUMENTS
-
-## Smart Task Addition
-
-Parse natural language to create well-structured tasks.
-
-### 1. **Input Understanding**
-
-I'll intelligently parse your request:
-- Natural language → Structured task
-- Detect priority from keywords (urgent, ASAP, important)
-- Infer dependencies from context
-- Suggest complexity based on description
-- Determine task type (feature, bug, refactor, test, docs)
-
-### 2. **Smart Parsing Examples**
-
-**"Add urgent task to fix login bug"**
-→ Title: Fix login bug
-→ Priority: high
-→ Type: bug
-→ Suggested complexity: medium
-
-**"Create task for API documentation after task 23 is done"**
-→ Title: API documentation
-→ Dependencies: [23]
-→ Type: documentation
-→ Priority: medium
-
-**"Need to refactor auth module - depends on 12 and 15, high complexity"**
-→ Title: Refactor auth module
-→ Dependencies: [12, 15]
-→ Complexity: high
-→ Type: refactor
-
-### 3. **Context Enhancement**
-
-Based on current project state:
-- Suggest related existing tasks
-- Warn about potential conflicts
-- Recommend dependencies
-- Propose subtasks if complex
-
-### 4. **Interactive Refinement**
-
-```yaml
-Task Preview:
-─────────────
-Title: [Extracted title]
-Priority: [Inferred priority]
-Dependencies: [Detected dependencies]
-Complexity: [Estimated complexity]
-
-Suggestions:
-- Similar task #34 exists, consider as dependency?
-- This seems complex, break into subtasks?
-- Tasks #45-47 work on same module
-```
-
-### 5. **Validation & Creation**
-
-Before creating:
-- Validate dependencies exist
-- Check for duplicates
-- Ensure logical ordering
-- Verify task completeness
-
-### 6. **Smart Defaults**
-
-Intelligent defaults based on:
-- Task type patterns
-- Team conventions
-- Historical data
-- Current sprint/phase
-
-Result: High-quality tasks from minimal input.