@sinoia/hubdoc-tools 1.0.4 → 1.2.1

package/plugins/onedrive/TESTING.md

@@ -1,197 +0,0 @@
-# Guide de test du plugin OneDrive
-
-Ce guide vous permet de tester le plugin OneDrive avec Microsoft Graph API.
-
-## Prérequis
-
-1. **Azure CLI installé** : `brew install azure-cli` (macOS) ou voir [docs Azure](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli)
-2. **Compte Microsoft/Office 365** avec accès OneDrive
-3. **HubDoc Tools configuré**
-
-> ⚠️ **Note** : Pour un test rapide, seul Azure CLI est nécessaire. L'enregistrement d'application Azure AD n'est requis que pour une intégration production.
-
-## Configuration de test
-
-### 1. Enregistrer une application Azure AD
-
-1. Aller sur [Azure Portal](https://portal.azure.com)
-2. Naviguer vers **Azure Active Directory** → **App registrations**
-3. Cliquer **New registration**
-4. Configurer les permissions Microsoft Graph :
-   - `Files.Read.All` (pour lire tous les fichiers)
-   - `Sites.Read.All` (pour SharePoint)
-   - `User.Read` (pour les informations utilisateur)
-
-### 2. Obtenir un token d'accès (Test rapide avec Azure CLI)
-
-```bash
-# Installer Azure CLI si nécessaire
-brew install azure-cli
-
-# Se connecter à votre compte Microsoft/Office 365
-az login
-
-# Obtenir un token pour Microsoft Graph
-az account get-access-token --resource https://graph.microsoft.com/
-```
-
-La commande retournera un JSON avec le token dans le champ `accessToken` :
-```json
-{
-  "accessToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIs...",
-  "expiresOn": "2025-01-10 15:30:00.000000",
-  ...
-}
-```
-
-### 3. Configuration pour test rapide
-
-Pour un test avec Azure CLI (pas besoin d'enregistrer d'app) :
-
-```json
-{
-  "clientId": "dummy",
-  "clientSecret": "dummy", 
-  "tenantId": "dummy",
-  "accessToken": "YOUR_TOKEN_FROM_AZ_CLI_COMMAND",
-  "rootPath": "/",
-  "limit": 10
-}
-```
-
-> 💡 Les champs `clientId`, `clientSecret`, et `tenantId` peuvent être des valeurs factices quand vous utilisez un token direct d'Azure CLI.
-
-### 4. Tester la connexion
-
-```bash
-# Lister les plugins disponibles
-npm run dev -- plugins
-
-# Vérifier que OneDrive est bien listé
-```
-
-### 5. Scanner les documents (test rapide)
-
-Utiliser le script de test :
-
-```bash
-# Modifier le fichier test-onedrive.js avec vos vraies valeurs
-node test-onedrive.js
-```
-
-## Résultats attendus
-
-### Scan réussi
-- ✅ Connection: SUCCESS
-- ✅ Documents trouvés avec métadonnées OneDrive
-- ✅ Limitation respectée (paramètre `limit`)
-- ✅ Types de documents variés (Office, PDF, images, etc.)
-
-### Structure des documents
-- **Chemin** : Structure de dossiers OneDrive/SharePoint
-- **Métadonnées** : OneDrive ID, download URL, parent path
-- **Types MIME** : Détection automatique basée sur l'extension
-
-## Test d'intégration complète
-
-### 1. Configuration d'une connexion
-```bash
-echo '{
-  "clientId": "YOUR_CLIENT_ID",
-  "clientSecret": "YOUR_CLIENT_SECRET", 
-  "tenantId": "YOUR_TENANT_ID",
-  "accessToken": "YOUR_TOKEN",
-  "rootPath": "/Documents",
-  "limit": 10
-}' > onedrive-config.json
-
-npm run dev -- connect onedrive --config onedrive-config.json --name test-onedrive
-```
-
-### 2. Scan des documents
-```bash
-npm run dev -- plugin-scan test-onedrive --output onedrive-mapping.csv
-```
-
-### 3. Vérification du mapping
-```bash
-head -10 onedrive-mapping.csv
-```
-
-Le fichier doit contenir :
-- Colonnes : File Path, Target Folder, Workspace, Metadata (JSON), Permissions
-- Métadonnées JSON avec OneDrive ID, download URL
-- Chemins organisés selon la structure OneDrive
-
-## Dépannage
-
-### Token expiré
-```
-Error: Request failed with status code 401
-```
-→ Renouveler le token avec `az account get-access-token --resource https://graph.microsoft.com/`
-
-### Permissions insuffisantes
-```
-Error: Insufficient privileges to complete the operation
-```
-→ Vérifier les permissions Microsoft Graph de l'application Azure
-
-### Dossier introuvable
-```
-Error: The resource could not be found
-```
-→ Vérifier le `rootPath` ou utiliser `/` pour la racine
-
-### Limite de débit
-```
-Error: Too many requests
-```
-→ Le plugin a déjà des délais intégrés, augmenter si nécessaire
-
-## Performance
-
-Avec limit=10 :
-- Durée : ~2-3 secondes
-- Documents : 10 maximum  
-- API calls : 1-2 requêtes
-
-Avec limit=100 :
-- Durée : ~10-15 secondes
-- Documents : 100 maximum
-- API calls : Pagination automatique
-
-## Paramètres utiles
-
-- **limit** : Nombre max de documents (utile pour tests)
-- **rootPath** : Dossier spécifique à scanner (ex: `/Documents`)
-- **accessToken** : Token direct (évite l'OAuth flow complexe)
-- **clientId/clientSecret** : Pour l'authentification OAuth2
-
-## Types de documents OneDrive observés
-
-- **Office** : .docx, .xlsx, .pptx (exportés automatiquement)
-- **PDF** : Documents PDF
-- **Images** : .jpg, .png, .gif
-- **Archives** : .zip, .rar
-- **Texte** : .txt, .csv, .json
-
-## Différences avec SharePoint
-
-Le plugin fonctionne pour :
-- **OneDrive personnel** : `/me/drive/`
-- **SharePoint** : Modifier l'URL de base si nécessaire
-- **OneDrive Entreprise** : Même API que personnel
-
-## Commandes utiles
-
-```bash
-# Test rapide de connexion
-node test-onedrive.js
-
-# Scan avec limite
-npm run dev -- plugin-scan test-onedrive --limit 5
-
-# Import vers dossier local
-npm run dev -- plugin-import test-onedrive ./downloads --limit 3
-```

package/plugins/onedrive/plugin.json

@@ -1,12 +0,0 @@
-{
-  "name": "onedrive",
-  "version": "1.0.0", 
-  "description": "Microsoft OneDrive document source plugin",
-  "author": "HubDoc Tools",
-  "main": "index.js",
-  "hubdocToolVersion": "^1.0.0",
-  "dependencies": {
-    "axios": "^1.5.0",
-    "fs-extra": "^11.1.0"
-  }
-}

package/scripts/build-windows-installer.ps1

@@ -1,132 +0,0 @@
-# Build Windows Installer for HubDoc Tool
-# PowerShell script for Windows users
-
-param(
-    [switch]$SkipTests,
-    [switch]$BuildInstaller
-)
-
-Write-Host "🚀 Building HubDoc Tool Windows Package..." -ForegroundColor Cyan
-
-# Check if we're in the right directory
-if (-not (Test-Path "package.json")) {
-    Write-Host "❌ Error: package.json not found. Please run from project root." -ForegroundColor Red
-    exit 1
-}
-
-Write-Host "📦 Step 1: Installing dependencies..." -ForegroundColor Blue
-npm install
-if ($LASTEXITCODE -ne 0) {
-    Write-Host "❌ npm install failed!" -ForegroundColor Red
-    exit 1
-}
-
-Write-Host "🔨 Step 2: Building TypeScript..." -ForegroundColor Blue
-npm run build
-if ($LASTEXITCODE -ne 0) {
-    Write-Host "❌ TypeScript build failed!" -ForegroundColor Red
-    exit 1
-}
-
-if (-not $SkipTests) {
-    Write-Host "📐 Step 3: Running tests..." -ForegroundColor Blue
-    npm run test-connectors
-    if ($LASTEXITCODE -ne 0) {
-        Write-Host "⚠️ Some tests failed, but continuing..." -ForegroundColor Yellow
-    }
-}
-
-Write-Host "🎯 Step 4: Creating Windows executable..." -ForegroundColor Blue
-npm run pkg
-if ($LASTEXITCODE -ne 0) {
-    Write-Host "❌ PKG build failed!" -ForegroundColor Red
-    exit 1
-}
-
-Write-Host "📊 Step 5: Creating multi-platform executables..." -ForegroundColor Blue
-npm run pkg:all
-if ($LASTEXITCODE -ne 0) {
-    Write-Host "⚠️ Multi-platform build partially failed" -ForegroundColor Yellow
-}
-
-# Check build artifacts
-Write-Host "📏 Step 6: Checking build artifacts..." -ForegroundColor Blue
-Get-ChildItem -Path "build" -File | Format-Table Name, @{Label="Size (MB)"; Expression={[math]::Round($_.Length/1MB, 2)}}
-
-# Create LICENSE if it doesn't exist
-if (-not (Test-Path "LICENSE")) {
-    Write-Host "📜 Creating LICENSE file..." -ForegroundColor Yellow
-    @"
-MIT License
-
-Copyright (c) 2024 Sinoia
-
-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.
-"@ | Out-File -FilePath "LICENSE" -Encoding UTF8
-}
-
-# Build NSIS installer if requested and available
-if ($BuildInstaller) {
-    Write-Host "🏗️ Step 7: Building NSIS installer..." -ForegroundColor Blue
-    
-    # Check if NSIS is installed
-    $nsisPath = Get-Command "makensis" -ErrorAction SilentlyContinue
-    if ($nsisPath) {
-        Set-Location "installer"
-        & makensis "hubdoc-tool.nsi"
-        Set-Location ".."
-        
-        if ($LASTEXITCODE -eq 0) {
-            Write-Host "✅ NSIS installer created successfully!" -ForegroundColor Green
-        } else {
-            Write-Host "❌ NSIS installer build failed!" -ForegroundColor Red
-        }
-    } else {
-        Write-Host "⚠️ NSIS not found. Install from https://nsis.sourceforge.io/" -ForegroundColor Yellow
-        Write-Host "   Then run: makensis installer/hubdoc-tool.nsi" -ForegroundColor Yellow
-    }
-}
-
-Write-Host "✅ Build completed successfully!" -ForegroundColor Green
-Write-Host ""
-Write-Host "📋 Build Summary:" -ForegroundColor Blue
-
-if (Test-Path "build/hubdoc-tool-windows.exe") {
-    $size = [math]::Round((Get-Item "build/hubdoc-tool-windows.exe").Length/1MB, 1)
-    Write-Host "  ✓ Windows executable: build/hubdoc-tool-windows.exe ($size MB)" -ForegroundColor Green
-}
-
-if (Test-Path "build/HubDoc-Tool-1.0.0-Setup.exe") {
-    $size = [math]::Round((Get-Item "build/HubDoc-Tool-1.0.0-Setup.exe").Length/1MB, 1)
-    Write-Host "  ✓ Windows installer: build/HubDoc-Tool-1.0.0-Setup.exe ($size MB)" -ForegroundColor Green
-}
-
-Write-Host ""
-Write-Host "🎯 Next Steps:" -ForegroundColor Blue
-Write-Host "  1. Test executable: build\hubdoc-tool-windows.exe --help"
-Write-Host "  2. Distribute to clients via:"
-Write-Host "     • Standalone .exe (no installation required)"
-Write-Host "     • Full installer .exe (with start menu, PATH, etc.)"
-Write-Host ""
-Write-Host "📚 Documentation included:" -ForegroundColor Blue
-Write-Host "  • docs/README.md - Overview"
-Write-Host "  • docs/connectors/ - Connector guides" 
-Write-Host "  • config-examples/ - Configuration templates"
-Write-Host ""
-Write-Host "🎉 Ready for distribution!" -ForegroundColor Green

package/scripts/build-windows-installer.sh

@@ -1,106 +0,0 @@
-#!/bin/bash
-
-# Build Windows Installer for HubDoc Tool
-# This script creates both a standalone executable and a Windows installer
-
-echo "🚀 Building HubDoc Tool Windows Installer..."
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-BLUE='\033[0;34m'
-NC='\033[0m' # No Color
-
-# Check if we're in the right directory
-if [ ! -f "package.json" ]; then
-    echo -e "${RED}❌ Error: package.json not found. Please run from project root.${NC}"
-    exit 1
-fi
-
-echo -e "${BLUE}📦 Step 1: Installing dependencies...${NC}"
-npm install
-
-echo -e "${BLUE}🔨 Step 2: Building TypeScript...${NC}"
-npm run build
-if [ $? -ne 0 ]; then
-    echo -e "${RED}❌ TypeScript build failed!${NC}"
-    exit 1
-fi
-
-echo -e "${BLUE}📐 Step 3: Running tests...${NC}"
-npm run test-connectors
-if [ $? -ne 0 ]; then
-    echo -e "${YELLOW}⚠️ Some tests failed, but continuing...${NC}"
-fi
-
-echo -e "${BLUE}🎯 Step 4: Creating standalone executable...${NC}"
-npm run pkg
-if [ $? -ne 0 ]; then
-    echo -e "${RED}❌ PKG build failed!${NC}"
-    exit 1
-fi
-
-echo -e "${BLUE}📊 Step 5: Creating multi-platform executables...${NC}"
-npm run pkg:all
-if [ $? -ne 0 ]; then
-    echo -e "${YELLOW}⚠️ Multi-platform build failed, but Windows exe exists${NC}"
-fi
-
-# Check file sizes
-echo -e "${BLUE}📏 Step 6: Checking build artifacts...${NC}"
-ls -lh build/
-
-# Create license file if it doesn't exist
-if [ ! -f "LICENSE" ]; then
-    echo -e "${YELLOW}📜 Creating LICENSE file...${NC}"
-    cat > LICENSE << 'EOF'
-MIT License
-
-Copyright (c) 2024 Sinoia
-
-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.
-EOF
-fi
-
-echo -e "${GREEN}✅ Build completed successfully!${NC}"
-echo ""
-echo -e "${BLUE}📋 Build Summary:${NC}"
-echo -e "  ${GREEN}✓${NC} Standalone Windows executable: ${YELLOW}build/hubdoc-tool-windows.exe${NC}"
-
-if [ -f "build/hubdoc-tool-linux" ]; then
-    echo -e "  ${GREEN}✓${NC} Linux executable: ${YELLOW}build/hubdoc-tool-linux${NC}"
-fi
-
-if [ -f "build/hubdoc-tool-macos" ]; then
-    echo -e "  ${GREEN}✓${NC} macOS executable: ${YELLOW}build/hubdoc-tool-macos${NC}"
-fi
-
-echo ""
-echo -e "${BLUE}🎯 Next Steps:${NC}"
-echo -e "  1. Test the Windows executable: ${YELLOW}./build/hubdoc-tool-windows.exe --help${NC}"
-echo -e "  2. For NSIS installer, install NSIS and run: ${YELLOW}makensis installer/hubdoc-tool.nsi${NC}"
-echo -e "  3. Distribute the executable or installer to clients"
-echo ""
-echo -e "${BLUE}📚 Documentation:${NC}"
-echo -e "  • User Guide: ${YELLOW}docs/README.md${NC}"
-echo -e "  • Connector Docs: ${YELLOW}docs/connectors/${NC}"
-echo -e "  • Config Examples: ${YELLOW}config-examples/${NC}"
-echo ""
-echo -e "${GREEN}🎉 Ready for distribution!${NC}"

package/scripts/prepare-publish.js

@@ -1,62 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Script de préparation pour la publication NPM
- * Prépare le package.json pour la publication sous @sinoia/hubdoc-tools
- */
-
-const fs = require('fs');
-const path = require('path');
-
-const packagePath = path.join(__dirname, '..', 'package.json');
-const packageJson = JSON.parse(fs.readFileSync(packagePath, 'utf8'));
-
-console.log('🔧 Preparing package for publication...');
-
-// Sauvegarder l'original
-const backupPath = packagePath + '.backup';
-fs.writeFileSync(backupPath, JSON.stringify(packageJson, null, 2));
-console.log(`💾 Backup saved to ${backupPath}`);
-
-// Modifier pour la publication
-const publishPackage = {
-  ...packageJson,
-  name: '@sinoia/hubdoc-tools',
-  publishConfig: {
-    access: 'public',
-    registry: 'https://registry.npmjs.org/'
-  },
-  // Ajouter des keywords pour la découverte
-  keywords: [
-    ...packageJson.keywords,
-    'sinoia',
-    'corex',
-    'document-management',
-    'file-import',
-    'bulk-upload',
-    'cli-tool'
-  ],
-  // S'assurer que le repository est correct
-  repository: {
-    type: 'git',
-    url: 'https://gitlab.com/sinoia/hubdoc-tools.git'
-  },
-  // Ajouter la page d'accueil
-  homepage: 'https://gitlab.com/sinoia/hubdoc-tools#readme',
-  // Informations sur les bugs
-  bugs: {
-    url: 'https://gitlab.com/sinoia/hubdoc-tools/-/issues'
-  }
-};
-
-// Écrire le package.json modifié
-fs.writeFileSync(packagePath, JSON.stringify(publishPackage, null, 2));
-
-console.log('✅ Package prepared for publication:');
-console.log(`   Name: ${publishPackage.name}`);
-console.log(`   Version: ${publishPackage.version}`);
-console.log(`   Registry: ${publishPackage.publishConfig.registry}`);
-console.log(`   Access: ${publishPackage.publishConfig.access}`);
-
-console.log('\n📦 Ready for: npm publish');
-console.log('🔄 To restore: node scripts/restore-package.js');

package/scripts/restore-package.js

@@ -1,29 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Script de restauration du package.json original
- * Restaure le package.json depuis la sauvegarde
- */
-
-const fs = require('fs');
-const path = require('path');
-
-const packagePath = path.join(__dirname, '..', 'package.json');
-const backupPath = packagePath + '.backup';
-
-console.log('🔄 Restoring original package.json...');
-
-if (!fs.existsSync(backupPath)) {
-  console.error('❌ No backup found at', backupPath);
-  process.exit(1);
-}
-
-// Restaurer depuis la sauvegarde
-const backup = fs.readFileSync(backupPath, 'utf8');
-fs.writeFileSync(packagePath, backup);
-
-// Supprimer la sauvegarde
-fs.unlinkSync(backupPath);
-
-console.log('✅ Original package.json restored');
-console.log('🗑️  Backup removed');