Add initial HTML template for MojeGS1 application with Cookiebot and Google Analytics integration

This commit is contained in:
2026-02-24 23:32:19 +01:00
parent 18d0019c28
commit 12f0c262c8
67 changed files with 50193 additions and 230 deletions

1
.serena/.gitignore vendored Normal file
View File

@@ -0,0 +1 @@
/cache

View File

@@ -0,0 +1,17 @@
# Handover: Integracja MojeGS1 — przypisywanie EAN
## Status: ZAIMPLEMENTOWANE (core flow)
## Co zostalo zaimplementowane:
1. `src/Modules/GS1/MojeGS1Client.php` — klient HTTP Basic Auth (cURL), listProducts, getProduct, upsertProduct, findHighestGtin, generateNextEan, calculateEan13CheckDigit
2. `src/Modules/GS1/GS1Service.php` — assignEanToProduct: sprawdza brak EAN, pobiera credentials z app_settings, generuje next EAN, rejestruje w GS1 API, zapisuje EAN lokalnie
3. `src/Modules/Products/ProductRepository.php` — dodano updateEan(int $id, string $ean)
4. `src/Modules/Products/ProductsController.php` — dodano assignGs1Ean method, wstrzyknięto GS1Service
5. `routes/web.php` — POST /products/{id}/assign-ean, wiring GS1Service
6. `resources/views/products/show.php` — przycisk "Przypisz EAN z GS1" gdy EAN pusty
7. `resources/lang/pl.php` — klucze products.gs1.*
## Co jeszcze do zrobienia (opcjonalne):
- Strona ustawień GS1 (formularz w settings do zarządzania credentials)
- Migracja app_settings z domyślnymi wartościami GS1
- Możliwość bulk-assign EAN dla wielu produktów naraz

View File

@@ -0,0 +1,142 @@
# Plan integracji MojeGS1 API - przypisywanie EAN z poziomu orderPRO
## Cel
Przycisk "Przypisz EAN z GS1" na stronie szczegółów produktu (`/products/{id}`), który automatycznie generuje kolejny EAN z puli GS1, rejestruje produkt w MojeGS1 i zapisuje EAN lokalnie.
## API MojeGS1 v2
- **Base URL:** `https://mojegs1.pl/api/v2`
- **Auth:** HTTP Basic (login + hasło)
- **Spec:** `/api/v2/swagger/external-api/swagger.json`
### Endpointy używane:
- `GET /api/v2/products?page[offset]=X&page[limit]=100&sort=name` — lista produktów (paginacja)
- `GET /api/v2/products/{Gtin}` — pojedynczy produkt
- `PUT /api/v2/products/{Gtin}` — utwórz/aktualizuj produkt
### Wymagane pola PUT:
- `brandName` (2-200 znaków) — marka
- `gpcCode` (8-cyfrowy int) — kod klasyfikacji GPC
- `netContent` (number) + `netContentUnit` (string: szt, kg, g, l, ml, m, cm, mm, m2, m3)
- `status` — "ACT" / "WIT" / "HID"
- `targetMarket` — array, np. ["PL"]
- `descriptionLanguage` — "PL"
- `description` — opis (20-4000 znaków, opcjonalne ale zalecane)
- `commonName` — nazwa zwyczajowa (do 150 znaków)
### Struktura request PUT:
```json
{
"data": {
"type": "products",
"id": "{GTIN-13}",
"attributes": {
"brandName": "marianek.pl",
"commonName": "Nazwa produktu",
"gpcCode": 10008365,
"netContent": 1,
"netContentUnit": "szt",
"status": "ACT",
"targetMarket": ["PL"],
"descriptionLanguage": "PL"
}
}
}
```
## Stan konta GS1
- 461 produktów zarejestrowanych
- **Główny prefiks:** `590532390` (9 cyfr, 451 produktów, ciągła sekwencja 000-450)
- Drugi prefiks: `590531617` (10 produktów, starsze)
- Najwyższy GTIN: `5905323904507` (item 450)
- Następny wolny: `5905323904514` (item 451)
- Max capacity: 1000 produktów (item 000-999)
## Dane dostępowe API
- Login: `user_85c27342-bc97-4f42-8890-f6b27d3233c4`
- Hasło: `K3sawGA3X?L?e^bJ$ZqyhieFG)w#c8f+?V^z`
- **UWAGA:** dane przechowywane w tabeli `app_settings`, NIE w kodzie
## Plan implementacji
### Krok 1: Tabela app_settings — migracja
Plik: `database/migrations/20260224_000013_add_gs1_settings.sql`
Dodać rekordy do `app_settings`:
- `gs1_api_login` — login API
- `gs1_api_password` — hasło API (zaszyfrowane lub plain — zależy od obecnego wzorca)
- `gs1_prefix` — prefiks GS1 (domyślnie `590532390`)
- `gs1_default_brand` — domyślna marka (domyślnie `marianek.pl`)
- `gs1_default_gpc_code` — domyślny kod GPC (domyślnie `10008365`)
Sprawdzić czy tabela `app_settings` już istnieje (migracja 000012).
### Krok 2: Strona ustawień GS1
Plik widoku: `resources/views/settings/gs1.php`
Pliki PHP: zmiana w `SettingsController.php` — dodać metody `gs1()` i `gs1Save()`
Route: `GET /settings/gs1` + `POST /settings/gs1`
Formularz z polami: login, hasło, prefiks, domyślna marka, domyślny kod GPC.
Przycisk "Test połączenia" (opcjonalnie).
### Krok 3: Klient MojeGS1
Plik: `src/Modules/GS1/MojeGS1Client.php`
Metody:
- `listProducts(int $page, int $limit): array` — lista produktów
- `getProduct(string $gtin): ?array` — pojedynczy produkt
- `upsertProduct(string $gtin, array $attributes): array` — PUT produkt
- `findHighestGtin(string $prefix): ?string` — paginuje i szuka max GTIN z prefiksu
- `generateNextEan(string $prefix): string` — oblicza kolejny EAN z cyfrą kontrolną
Statyczna metoda:
- `calculateEan13CheckDigit(string $partial12): int`
### Krok 4: Serwis GS1
Plik: `src/Modules/GS1/GS1Service.php`
Metoda: `assignEanToProduct(int $productId): array`
1. Pobierz produkt z orderPRO (sprawdź czy nie ma już EAN)
2. Pobierz ustawienia GS1 z app_settings
3. Znajdź najwyższy GTIN w GS1 API
4. Wygeneruj następny EAN
5. Zarejestruj w GS1 (PUT) z danymi produktu (nazwa, marka, gpcCode)
6. Zaktualizuj EAN w produkcie orderPRO
7. Zwróć nowy EAN
### Krok 5: Controller endpoint
Plik: `src/Modules/Products/ProductsController.php`
Nowa metoda: `assignGs1Ean(Request $request): Response`
Route: `POST /products/{id}/assign-ean`
- Walidacja CSRF
- Wywołanie GS1Service::assignEanToProduct
- Flash success/error
- Redirect back do `/products/{id}`
### Krok 6: Widok — przycisk na stronie produktu
Plik: `resources/views/products/show.php`
Dodać przycisk "Przypisz EAN z GS1" widoczny gdy `$product['ean']` jest pusty.
Formularz POST do `/products/{id}/assign-ean`.
### Krok 7: Tłumaczenia
Plik: `resources/lang/pl.php`
Dodać klucze:
- `products.gs1.assign_ean` — "Przypisz EAN z GS1"
- `products.gs1.ean_assigned` — "EAN :ean został przypisany i zarejestrowany w GS1."
- `products.gs1.already_has_ean` — "Produkt ma już przypisany EAN."
- `products.gs1.error` — "Błąd podczas przypisywania EAN z GS1."
- `settings.gs1.*` — etykiety formularza ustawień
### Krok 8: Routing
Plik: `routes/web.php`
Dodać:
- `POST /products/{id}/assign-ean` → ProductsController::assignGs1Ean
- `GET /settings/gs1` → SettingsController::gs1
- `POST /settings/gs1` → SettingsController::gs1Save
## Zależności
- `AppSettingsRepository` — już istnieje (migracja 000012), sprawdzić API
- `ProductRepository` — metoda update EAN (sprawdzić czy istnieje)
- Curl extension — wymagany (prawdopodobnie już jest)
## Kolejność prac
1 → 3 → 4 → 5 → 6 → 7 → 8 → 2 (ustawienia na końcu, na początku hardcode credentials do testów)
Praktycznie: 3 → 4 → 5 → 6 → 7 → 8 (migracja i ustawienia mogą być równolegle)

126
.serena/project.yml Normal file
View File

@@ -0,0 +1,126 @@
# the name by which the project can be referenced within Serena
project_name: "orderPRO"
# list of languages for which language servers are started; choose from:
# al bash clojure cpp csharp
# csharp_omnisharp dart elixir elm erlang
# fortran fsharp go groovy haskell
# java julia kotlin lua markdown
# matlab nix pascal perl php
# php_phpactor powershell python python_jedi r
# rego ruby ruby_solargraph rust scala
# swift terraform toml typescript typescript_vts
# vue yaml zig
# (This list may be outdated. For the current list, see values of Language enum here:
# https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py
# For some languages, there are alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
# Note:
# - For C, use cpp
# - For JavaScript, use typescript
# - For Free Pascal/Lazarus, use pascal
# Special requirements:
# Some languages require additional setup/installations.
# See here for details: https://oraios.github.io/serena/01-about/020_programming-languages.html#language-servers
# When using multiple languages, the first language server that supports a given file will be used for that file.
# The first language is the default language and the respective language server will be used as a fallback.
# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
languages:
- php
# the encoding used by text files in the project
# For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
encoding: "utf-8"
# The language backend to use for this project.
# If not set, the global setting from serena_config.yml is used.
# Valid values: LSP, JetBrains
# Note: the backend is fixed at startup. If a project with a different backend
# is activated post-init, an error will be returned.
language_backend:
# whether to use project's .gitignore files to ignore files
ignore_all_files_in_gitignore: true
# list of additional paths to ignore in this project.
# Same syntax as gitignore, so you can use * and **.
# Note: global ignored_paths from serena_config.yml are also applied additively.
ignored_paths: []
# whether the project is in read-only mode
# If set to true, all editing tools will be disabled and attempts to use them will result in an error
# Added on 2025-04-18
read_only: false
# list of tool names to exclude. We recommend not excluding any tools, see the readme for more details.
# Below is the complete list of tools for convenience.
# To make sure you have the latest list of tools, and to view their descriptions,
# execute `uv run scripts/print_tool_overview.py`.
#
# * `activate_project`: Activates a project by name.
# * `check_onboarding_performed`: Checks whether project onboarding was already performed.
# * `create_text_file`: Creates/overwrites a file in the project directory.
# * `delete_lines`: Deletes a range of lines within a file.
# * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
# * `execute_shell_command`: Executes a shell command.
# * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
# * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
# * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
# * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
# * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
# * `initial_instructions`: Gets the initial instructions for the current project.
# Should only be used in settings where the system prompt cannot be set,
# e.g. in clients you have no control over, like Claude Desktop.
# * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
# * `insert_at_line`: Inserts content at a given line in a file.
# * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
# * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
# * `list_memories`: Lists memories in Serena's project-specific memory store.
# * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
# * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
# * `read_file`: Reads a file within the project directory.
# * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
# * `remove_project`: Removes a project from the Serena configuration.
# * `replace_lines`: Replaces a range of lines within a file with new content.
# * `replace_symbol_body`: Replaces the full definition of a symbol.
# * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
# * `search_for_pattern`: Performs a search for a pattern in the project.
# * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
# * `switch_modes`: Activates modes by providing a list of their names
# * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
# * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
# * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
# * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
excluded_tools: []
# list of tools to include that would otherwise be disabled (particularly optional tools that are disabled by default)
included_optional_tools: []
# fixed set of tools to use as the base tool set (if non-empty), replacing Serena's default set of tools.
# This cannot be combined with non-empty excluded_tools or included_optional_tools.
fixed_tools: []
# list of mode names to that are always to be included in the set of active modes
# The full set of modes to be activated is base_modes + default_modes.
# If the setting is undefined, the base_modes from the global configuration (serena_config.yml) apply.
# Otherwise, this setting overrides the global configuration.
# Set this to [] to disable base modes for this project.
# Set this to a list of mode names to always include the respective modes for this project.
base_modes:
# list of mode names that are to be activated by default.
# The full set of modes to be activated is base_modes + default_modes.
# If the setting is undefined, the default_modes from the global configuration (serena_config.yml) apply.
# Otherwise, this overrides the setting from the global configuration (serena_config.yml).
# This setting can, in turn, be overridden by CLI parameters (--mode).
default_modes:
# initial prompt for the project. It will always be given to the LLM upon activating the project
# (contrary to the memories, which are loaded on demand).
initial_prompt: ""
# time budget (seconds) per tool call for the retrieval of additional symbol information
# such as docstrings or parameter information.
# This overrides the corresponding setting in the global configuration; see the documentation there.
# If null or missing, use the setting from the global configuration.
symbol_info_budget: