Skip to content
CAI
Software that uses CAICheck a score

Volmarg/personal-management-system

39.6

Weak · 17 November 2026

27.1k

lines of production code

PHP

primary language

5

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add API for managing module lock settings

A new endpoint at /module/system/settings/modules/lock allows users to retrieve and update the lock status of system modules. The GET /all route returns the current lock state for all modules, while the PATCH / route enables updating these settings, provided the system is not locked and the environment is not in demo mode (where updates are denied).

src/Action/Modules/System/Settings/Modules · high confidence

Add API for managing shopping plans

Users can now create, retrieve, update, and delete shopping plans via the new /module/shopping/plans endpoint. The API supports creating a plan with a name and information, fetching all active plans, updating existing plans, and soft-deleting plans by marking them as deleted.

src/Action/Modules/Shopping · high confidence

Add custom Doctrine type for serialized JSON storage

A new \SerializedJson\ Doctrine type has been introduced to handle the storage and retrieval of array data as serialized strings in the database. This allows entities to map array properties directly to a database column, automatically serializing them on write and unserializing them on read, with error handling for invalid data.

src/Entity/DoctrineTypes · high confidence

Added CollectionService to preserve array indexing after filtering

A new CollectionService has been introduced in the Doctrine layer to handle collection filtering. This utility ensures that when a Doctrine collection is filtered, the resulting array maintains numeric indexes. This prevents frontend issues where missing indexes might cause the data to be incorrectly interpreted as an object rather than an array.

src/Doctrine · high confidence

Added DoctorContactDto for health module data transfer

A new DoctorContactDto class has been introduced in the Health module to structure doctor contact information. This data transfer object includes fields for name, value, and a UUID, and utilizes the SerializerAwareTrait to facilitate serialization and deserialization processes for frontend consumption.

src/DTO/Modules/Health · high confidence

Added HP LaserJet CM1015 cMFP manual to demo data

The demo data module for Files now includes a PDF manual for the HP LaserJet CM1015 cMFP printer, located in the Documents/Manuals directory. This addition provides users with sample reference documentation within the application's file structure.

assets/static/demoData/modules/Files · high confidence

Added IncomingScheduleDTO for schedule data transfer

Introduced the IncomingScheduleDTO class in the Schedules module to structure incoming schedule data. This data transfer object encapsulates schedule attributes including ID, reminder ID, title, date, days difference, schedule type, icon, and body content, providing a standardized way to handle schedule information within the application.

src/DTO/Modules/Schedules · high confidence

Added data fixtures for Todo module entities

New Doctrine fixtures have been added to populate the database with sample data for the Todo module. MyTodoFixtures creates MyTodo entities linked to Goals and Issues modules, while MyTodoElementFixtures creates associated MyTodoElement records with completion statuses, ensuring the application has seed data for testing and initial setup.

src/DataFixtures/Modules/Todo · high confidence

Added data fixtures for files, settings, and icons

New data provider classes have been added to the \src/DataFixtures/Providers\ directory to support demo data generation. \FilesTags\ provides a static dataset mapping file paths to JSON-encoded tags for documents and images. \SettingProvider\ defines constants for supported currencies (PLN, EUR, CASH). \FontawesomeIconsProvider\ was added as a placeholder class with a \getRandomIcon\ method, though it currently returns an empty string.

src/DataFixtures/Providers · high confidence

Added demo data fixture for ModuleData entities

A new Doctrine data fixture (src/DataFixtures/Modules/ModuleData.php) has been added to populate the database with demo ModuleData entities. This fixture loads records from the ModuleDataProvider, creating ModuleDataEntity instances with record identifiers, module associations, record types, and descriptions, and persists them to the database.

src/DataFixtures/Modules · high confidence

Added demo data fixture for My Issues module

A new data fixture (\MyIssues\) has been introduced to populate the database with sample data for the My Issues module. When loaded, this fixture clears existing issue records and inserts demo data for issues, their associated contacts, and progress updates, facilitating easier local development and testing of the module's features.

src/DataFixtures/Modules/Issues · high confidence

Added demo data fixture for travel ideas

A new data fixture class, MyTravelsIdeasFixtures, has been introduced to populate the application with sample travel idea records. When loaded, this fixture generates 151 entries using Faker to create random countries, cities, and categories, while assigning a static map and a placeholder image from picsum.photos to each record.

src/DataFixtures/Modules/Travels · high confidence

Added demo data fixtures for Contacts, Achievements, and Shopping modules

New data fixtures have been introduced to populate the application with sample data for development and demonstration purposes. The Contacts fixture now generates demo contacts, groups, and types using Faker for realistic data generation. Additionally, new fixtures were added for the Achievements module to load predefined achievement types and for the Shopping module to create sample shopping plans based on expensive product examples.

src/DataFixtures/Modules/Contacts · high confidence

Added demo data fixtures for Goals and Passwords modules

New data fixtures have been added to populate the application with sample data for the Goals and Passwords modules. The \MyPasswordsSettingsFixtures\ creates password groups, \MyPasswordsFixtures\ generates individual password entries linked to those groups, and \MyGoalsPaymentsFixtures\ creates payment goal records with randomized dates and amounts. These fixtures allow users to quickly load demo data for testing and demonstration purposes.

src/DataFixtures/Modules/Goals, src/DataFixtures/Modules/Passwords · high confidence

Added demo data fixtures for My Notes categories and settings

New fixture classes have been added to populate the application with demo data for the My Notes module. MyNotesSettingsFixtures creates note categories with names, icons, colors, and parent-child relationships, while MyNotesFixtures generates individual notes linked to those categories. These fixtures allow users to quickly seed the database with sample content for testing and demonstration purposes.

src/DataFixtures/Modules/Notes · high confidence

Added demo data fixtures for job after-hours and holidays

New data fixtures have been added to populate the application with sample data for job-related modules. The \MyJobAfterhoursFixtures\ class generates random records for after-hours work, including both time made and time spent entries linked to specific goals. The \MyJobHolidaysFixtures\ class creates holiday pool records based on company configurations and adds sample records for spent holiday days. These fixtures allow users to quickly populate the system with realistic demo data for testing and demonstration purposes.

src/DataFixtures/Modules/Job · high confidence

Added demo data fixtures for the Payments module

New Doctrine fixtures have been added to populate the database with realistic demo data for the Payments module. This includes fixtures for bills (MyPaymentsBills), income (MyPaymentsIncome), monthly recurring payments and shopping transactions (MyPaymentsMonthly), money owed (MyPaymentsOwed), individual products (MyPaymentsProducts), and payment settings (MyPaymentsSettings). These fixtures ensure that the application starts with pre-configured categories, currency multipliers, and sample transaction records for testing and demonstration purposes.

src/DataFixtures/Modules/Payments · high confidence

Added demo data fixtures for users, settings, and file tags

New data fixtures have been added to populate the application with initial demo data. The UserFixtures class creates a default admin user with the username 'admin', email '[e-mail redacted]', and the SUPER\_ADMIN role. The SettingFixtures class initializes finance settings, including default currencies for PLN, EUR, and Cash. Additionally, the FilesTags fixture provides a provider for populating file-tag associations.

src/DataFixtures · high confidence

Added demo data generator for the new schedule system

A new data fixture (MyScheduleFixtures) has been added to populate the application with demo data for the updated schedule module. This generator creates sample calendars, schedules spanning previous, current, and next months, and associated reminders, ensuring the new schedule entities are populated with realistic test data during development or seeding.

src/DataFixtures/Modules/Schedule · high confidence

Added development and production JWT key pairs

The application now includes dedicated RSA key pairs for signing and verifying JSON Web Tokens in both development and production environments. New encrypted private keys and corresponding public keys have been added to the \config/jwt/dev\ and \config/jwt/prod\ directories, enabling distinct cryptographic identities for each environment to ensure secure token issuance and validation.

config/jwt · high confidence

Added development debug endpoint

A new DevAction class has been introduced to provide a debug route for the backend. When accessed, this endpoint returns a JSON response confirming the class and method name, serving as a simple verification tool for development environments.

src/Action · high confidence

Added system entities for resource locking and module management

Introduced two new Doctrine entities to support system-level configuration and concurrency control. The LockedResource entity enables tracking of locked resources by type, target, and record, ensuring unique constraints to prevent duplicate locks. The Module entity manages application modules with an active status flag and establishes a one-to-many relationship with MyTodo items, allowing modules to contain associated to-do lists.

src/Entity/System · high confidence

Automated scripts for rebuilding demo database and file assets

Added two new shell scripts, \cron-rebuild-database.bash\ and \cron-rebuild-files.bash\, to automate the reset of the demo environment. The database script drops and recreates the schema, runs migrations, clears specific contact and schedule tables, uploads storage module files, and appends fixtures. The file script clears the public upload directories for images, files, and videos, then repopulates them with static demo data and sets correct ownership and permissions.

private/demo · high confidence

Centralized module definitions and file-path mapping service

A new ModulesService has been introduced to centralize the list of available modules and their display names, ensuring consistent mapping between backend identifiers and frontend labels. This service also provides a utility to determine the specific module associated with a file upload path by analyzing the directory structure, supporting modules such as Images, Files, and Video.

src/Services/Module · high confidence

Dashboard widget visibility settings API

A new API endpoint has been added to manage which widgets are visible on the system dashboard. Users can now retrieve the current visibility state of all dashboard widgets via a GET request, which includes whether each widget's associated module is locked, and update these preferences via a PATCH request. This change enables users to customize their dashboard layout by enabling or disabling specific widgets.

src/Action/Modules/System/Settings/Dashboard · high confidence

Enable management of system finances currencies

Users can now create, update, and delete currency settings within the system finances module. This change introduces a new action class that exposes endpoints for listing all configured currencies, adding new ones, modifying existing entries, and removing them. The implementation enforces validation rules, such as preventing the deletion of the default currency and ensuring currency names remain unique, while leveraging dedicated services to load and save the finance settings.

src/Action/Modules/System/Settings · high confidence

Enable user profile and security settings updates

New action classes in src/Action/User/Setting now allow users to update their personal data (username), change their profile image, modify their email address, and update both their login and lock passwords. The email and password change endpoints are restricted in demo environments, and password changes require confirmation matching.

src/Action/User · high confidence

Expanded demo data providers for multiple modules

The demo data generation capabilities have been significantly expanded by introducing new fixture providers for several modules. New data sets are now available for Achievements (categorized by difficulty), Contact management (including groups, types, and color themes), Goals (payment-related), Issues (with progress tracking and contact logs), and Job-related modules (Afterhours and Holidays). These additions allow the application to populate these specific areas with realistic sample data for demonstration and testing purposes.

src/DataFixtures/Providers/Modules · high confidence

Initial Docker Compose setup for Raspberry Pi and standard environments

The project now includes dedicated Docker Compose files to support local development and deployment on different architectures. A new \docker-compose-pi.yml\ file provides an ARM32-optimized stack (using \linuxserver/mariadb:arm32v7\ and \yobasystems/alpine-nginx:armhf\) tailored for Raspberry Pi, including specific volume mounts for backups and host gateway access. A standard \docker-compose.yml\ is also introduced for general use, featuring MariaDB 11.5.2, Adminer, and a Mailpit service for email testing. These files establish the foundational infrastructure for running the Personal Management System locally.

(repo-wide) · high confidence

Initial implementation of Health module API endpoints

This change introduces the backend API controllers for the Health module, enabling users to manage doctors, illnesses, and doctor appointments. The new DoctorAction provides endpoints to create, update, retrieve, and soft-delete doctors, including support for doctor contacts and handling of unique constraint violations. The IllnessAction allows for managing illness records and their associated appointments, with soft-deletion cascading to linked appointments. The DoctorAppointmentAction enables creating, updating, retrieving, and soft-deleting appointments, as well as a dedicated endpoint for saving associated storage files. All endpoints return structured JSON responses and handle basic validation and error cases.

src/Action/Modules/Health · high confidence

Introduce BaseResponse class for standardized API responses

A new BaseResponse class has been added to the application to serve as the foundation for all API responses. This class standardizes the structure of responses sent to the frontend by enforcing a consistent JSON format that includes fields such as code, message, success status, and data. It integrates with the Symfony Serializer to handle serialization and includes support for JWT tokens and specific data keys like IDs and lock statuses, ensuring that the frontend can reliably parse and reconstruct response objects.

src/Response/Base · high confidence

Introduce PHP 8.3 FPM container with automated initialization and caching

The docker/php-fpm directory now provides a complete PHP 8.3 FPM environment that automatically handles container startup tasks. The new entrypoint script manages Composer dependency installation, database migration execution, and directory permission setup. It also generates encryption keys and JWT key pairs on first run, registers storage files into the database, and clears OPcache and APCu caches to ensure a clean state. The configuration includes PHP 8.3 with OPcache JIT enabled, APCu for user caching, and a tuned FPM pool configuration.

docker/php-fpm · high confidence

Introduce health domain entities for doctors, illnesses, and appointments

Added new Doctrine entities for the Health module: Doctor (with specialisation, name, address, contacts, and information), Illness (with name, information, and a collection of appointments that filters out soft-deleted records by default), and DoctorAppointment (linking a doctor and an illness with a date and optional information). All three entities implement SoftDeletableEntityInterface and use SoftDeleteAwareTrait, meaning records are marked as deleted rather than removed, and queries (such as Illness::getAppointments) respect this soft-delete state. Doctor and Illness entities also include unique constraints on their respective key fields to prevent duplicate records.

src/Entity/Modules/Health · high confidence

Introduced service classes for formatting My Issues and My Todo data

Added MyIssuesService and MyTodoService to handle the transformation of entity data into structured arrays for the frontend. MyIssuesService aggregates issue details, including associated contacts, progress logs, and related todo elements (subject to access control), while MyTodoService retrieves assignable modules/entries and formats todo items with their elements and module context.

src/Services/Module/Issues · high confidence

Introduction of new DTOs for contacts, validation, and notifications

The application now includes a new set of Data Transfer Objects in the src/DTO directory to standardize data handling. This introduces an AbstractDTO base class with JSON serialization capabilities, alongside specific DTOs for managing contact types (ContactTypeDto, ContactsTypesDto), database credentials (DatabaseCredentialsDTO), validation results (ValidationResultDto), and notifications (NotificationDto). These classes provide structured containers and serialization methods for their respective data domains.

src/DTO · high confidence

New API endpoint for managing travel ideas

A new controller action has been added to handle the creation, retrieval, updating, and deletion of travel ideas via a dedicated API endpoint at /module/travels/ideas. Users can now POST to create new ideas, GET to retrieve all non-deleted ideas, PATCH to update existing ones, and DELETE to soft-delete records. The endpoint enforces required fields for location, country, image URL, and category, while allowing the map URL to be optional.

src/Action/Modules/Travels · high confidence

New API endpoints for job afterhours, holidays, and holiday pools

Users can now manage job-related time-off records via new backend actions. The system exposes REST endpoints to create, read, update, and delete (soft-delete) afterhours entries (tracking minutes, goals, and dates), holiday days spent (tracking year, days, and information with validation), and holiday pool settings (tracking year, days, and company name). These changes enable the frontend to persist and retrieve these specific job module data structures.

src/Action/Modules/Job · high confidence

New API endpoints for managing contacts and contact types

This change introduces two new controller actions for the Contacts module: \ContactsAction\ and \ContactTypesAction\. \ContactsAction\ exposes endpoints to create, retrieve, update, and soft-delete contacts, including their associated group details and contact types. \ContactTypesAction\ provides specific endpoints to add, update, and remove individual contact types linked to a contact. These endpoints allow users to fully manage contact records and their associated type metadata via the API.

src/Action/Modules/Contacts · high confidence

New API endpoints for managing goals and goal payments

Users can now interact with the goals module via new backend actions. The system exposes endpoints to retrieve a list of all goals (mapped to 'my-goals') and to perform full CRUD operations on goal payments, including creating, updating, and soft-deleting payment records. These endpoints support JSON requests and responses, allowing frontend applications to manage goal-related data and dashboard visibility settings.

src/Action/Modules/Goals · high confidence

New API endpoints for managing monthly import profiles and filter rules

Users can now configure monthly payment imports through new backend endpoints. The system introduces Import Profile management (create, read, update, delete) to define field mappings for currency, description, money, and date fields. Additionally, Import Filter Rules can be managed, allowing users to define filtering logic (field name, rule, type) and optionally assign an import profile to each rule. These changes enable more structured and customizable monthly payment data imports.

src/Action/Modules/Payments/Settings/MonthlyPayment · high confidence

New API endpoints for managing payment bills and bill items

This change introduces two new controller classes, BillsAction and ItemsAction, which expose RESTful endpoints for the Payments module. Users can now create, retrieve, update, and soft-delete payment bills (with required fields like name, dates, and planned amount) and individual bill items (linked to a specific bill with date, name, and amount). The bills endpoint also returns bill items sorted by date.

src/Action/Modules/Payments/Bills · high confidence

New Job entity modules and enhanced Afterhours tracking

This change introduces new entity models for job-related data: MyJobHolidays (tracking days spent, information, and year with soft-delete support), MyJobSettings (key-value configuration), and MyJobHolidaysPool (renamed from MyCar, tracking year, days in pool, company name, and frozen status). It also significantly enhances the MyJobAfterhours entity by adding soft-delete capabilities, converting date handling to use DateTime objects with string parsing, renaming type constants to TYPE\_SPENT/TYPE\_MADE, and adding convenience methods to calculate seconds, hours, and days from the stored minutes.

src/Entity/Modules/Job · high confidence

New ModuleAttribute for controlling method access via locking

A new ModuleAttribute class has been introduced in src/Attribute to manage access control for action methods and classes. This attribute allows developers to specify a module name and related modules, enabling the system to check if a method should be executed based on whether the associated resource is locked or unlocked.

src/Attribute · high confidence

New ModuleData entity for storing module metadata

A new \ModuleData\ entity has been introduced to store descriptive metadata (such as descriptions) associated with modules and their records. This entity supports unique constraints on record type, module, and identifier, and includes a dedicated field for storing text descriptions, enabling users to add context to upload-based categories and other module entries.

src/Entity/Modules · high confidence

New ModuleDataRepository for managing module data entities

A new repository class, ModuleDataRepository, has been introduced to handle persistence and retrieval of ModuleData entities. This component provides specific methods to find module data by record type, module name, and record identifier, as well as standard operations to save entities and retrieve them by ID, facilitating the storage and access of module-specific configuration or metadata within the application.

src/Repository/Modules · high confidence

New My Issues module with CRUD endpoints for issues, contacts, and progress

This change introduces the backend API for a new 'My Issues' feature, adding three new controller actions: MyIssuesAction, MyIssuesContactAction, and MyIssuesProgressAction. Users can now create, update, and soft-delete issues via the /module/my-issues endpoint, and manage associated contact records and progress logs through /module/my-issues/contact and /module/my-issues/progress respectively. The implementation supports JSON-based requests for creating and updating records, including date and information fields, and returns standard JSON responses for all operations.

src/Action/Modules/Issues · high confidence

New MyIssue entity with soft-delete, dashboard visibility, and contact/progress tracking

This change introduces the MyIssue entity and its related MyIssueContact and MyIssueProgress entities, enabling users to create and manage issues with associated contact and progress records. The MyIssue entity supports soft deletion, includes a dashboard visibility toggle (showOnDashboard), and links to a MyTodo record. Users can now track issue details, contacts, and progress updates, with soft-deleted contacts automatically filtered out when viewing an issue.

src/Entity/Modules/Issues · high confidence

New array and text processing utilities added to TypeProcessor service

The TypeProcessor service now includes two new helper classes: ArrayHandler and TextHandler. ArrayHandler provides static methods to safely retrieve array keys with optional defaults or exceptions, and to generate cartesian products of input arrays. TextHandler adds functionality to shorten strings with ellipses and convert camelCase or PascalCase identifiers into human-readable titles, which is used for user-facing error messages regarding missing or empty fields.

src/Services/TypeProcessor · high confidence

New backend API for managing calendar schedules and calendars

This change introduces two new controller actions in the Calendar module: \SchedulesAction\ and \ManageCalendarsAction\. \SchedulesAction\ provides endpoints to create, update, and delete user schedules, including handling associated reminders and validating that schedules are linked to existing calendars. \ManageCalendarsAction\ allows users to manage calendar groups (create, update, delete) and retrieve a list of all active calendars with their associated schedules and color settings. These endpoints replace legacy schedule controllers and provide the necessary data structure for the frontend dashboard.

src/Action/Modules/Calendar · high confidence

New backend endpoints for managing personal todo lists and elements

The application now exposes dedicated API endpoints to create, read, update, and delete personal todo items and their sub-elements. Users can manage todo lists via the \/module/my-todo\ routes, which support linking a todo to a specific issue record and controlling its visibility on the dashboard. Additionally, the \/module/my-todo-element\ routes allow for the creation and modification of individual todo items within a list, automatically updating the parent list's completion status when elements are added, updated, or removed.

src/Action/Modules/Todo · high confidence

New command to sync storage files to database entities

A new console command, \storage:upload-files-into-entities\, has been added to automatically create database entries for files currently present in storage. When executed, the command iterates through all storage modules, constructs the correct file paths (handling cases where extensions may be missing), and persists new file records to the database via Doctrine, providing a table output of the added files upon completion.

src/Command/Module/Storage · high confidence

New cron commands for backups, resource monitoring, and data synchronization

This update introduces several new scheduled tasks in the application. Administrators can now generate separate backups for configuration files via the new \cron:make-config-backup\ command, distinct from the existing general backup command. A new \cron:check-server-resources\ command monitors disk space and logs an emergency alert if free space falls below a specified threshold. Additionally, new commands facilitate data synchronization: \cron:transfer-data-to-pms-io\ exports notes and passwords to the PMS-IO service, while \cron:transfer-schedules-to-notifier-proxy-logger\ sends schedule reminders to external channels like email or Discord. The \cron:set-recurring-payments\ command has also been added to handle recurring payment logic. Also in this area: 1 commit (0 fixes) modifying (repo-wide).

src/Command/Crons · low confidence · unverified

New database export and Doctrine utility services

Added DatabaseExporter to handle database dumps via shell commands, including safety checks for backup directory existence, minimum file size validation, and timestamped file prefixes to prevent overwrites. Added DoctrineService with a static helper to verify if an object implements EntityInterface.

src/Services/Database · high confidence

New entity marker and validation interfaces introduced

The application now includes a set of new interfaces in the \src/Entity/Interfaces\ directory to standardize entity behavior. \EntityInterface\ serves as a marker to identify classes as entities. \ValidateEntityInterface\, along with its specialized \ValidateEntityForCreateInterface\ and \ValidateEntityForUpdateInterface\, establishes a contract for external validation logic, ensuring that entities implementing these interfaces have corresponding validation handlers defined. Additionally, \FileStorageAssociationInterface\ defines methods for managing associations with \StorageFile\ objects, and \SoftDeletableEntityInterface\ provides a contract for soft-delete capabilities via \isDeleted\ and \setDeleted\ methods.

src/Entity/Interfaces · high confidence

New entity traits for timestamps, file associations, and soft deletion

Added three new reusable traits to the entity layer: \CreateModifyFieldAwareTrait\ provides automatic \created\ and \modified\ datetime columns with default timestamps; \FileStorageAssociationTrait\ enables entities to manage a collection of \StorageFile\ objects with add/remove operations; and \SoftDeleteAwareTrait\ introduces a \deleted\ boolean flag to support soft-deletable entities.

src/Entity/Trait · high confidence

New enums for monthly payment import field and rule types

Added two new enumerations to structure monthly payment imports: \ImportFieldEnum\ defines the supported data fields (date, money, description, currency), and \ImportRuleTypeEnum\ defines the available matching strategies for filter rules (regex, exact, partial).

src/Enum/Modules/Payments · high confidence

New exception logging and serialization traits

Added two new traits to the application: ExceptionLoggerAwareTrait, which provides a method to log critical exceptions with code, trace, and custom data, and SerializerAwareTrait, which offers private methods to serialize objects to JSON and deserialize JSON data into target classes using Symfony's Serializer component.

src/Traits · high confidence

New file archiving service for creating zip backups

A new \Archivizer\ service has been introduced in the \src/Services/Files/Archivizer\ directory to handle the creation of zip archives. This includes an abstract base class defining configuration options (such as target directories, file prefixes, and recursive archiving settings) and a concrete \ZipArchivizer\ implementation that uses PHP's \ZipArchive\ extension to bundle specified directories and files. The service includes safety checks, such as verifying the minimum archive size and handling permission errors, to ensure reliable backup generation.

src/Services/Files/Archivizer · high confidence

New file path and storage module services

The Files service area now includes two new classes: FilesHandler, which provides utility methods for normalizing directory and file paths (trimming or adding slashes), and PathService, which centralizes logic for determining upload directories for files, images, and videos, resolving storage modules from file paths, and validating path safety to prevent directory traversal attacks.

src/Services/Files · high confidence

New file upload, configuration, and deletion endpoints

A new UploadedFileAction controller introduces three endpoints for managing file uploads: POST /upload/send/ accepts base64-encoded file content, optional user-defined names, and tags, storing the file and returning its path (with a demo-mode safeguard that deletes uploaded files immediately); GET /upload/get-configuration/{id} retrieves upload configuration details; and GET /upload/delete/{filePath} removes a file after validating path safety. This change adds new API capabilities for uploading, configuring, and deleting files, including support for tagging files during upload.

src/Action/File · high confidence

New import profile and filter rule entities for monthly payments

The monthly payments module now includes data structures to support configurable import profiles. The new ImportProfile entity allows users to define which fields correspond to dates, amounts, descriptions, and currencies, while the ImportFilterRule entity enables the definition of filtering logic tied to specific profiles. These entities establish the foundational schema for mapping and filtering incoming monthly payment data.

src/Entity/Modules/Payments/Monthly · high confidence

New payment report endpoints for historical debts and monthly totals

This change introduces three new API endpoints under the Reports module to expose payment data for client-side visualization. The HistoricallyOwedMoneyAction endpoint (GET /module/reports/money-owed/historical/all) retrieves a list of historically owed money entries, including target, amount, currency, and dates. The MonthlyPerTypeAction endpoint (GET /module/reports/payments/total-per-type/all) provides total payment amounts grouped by type, with missing months filled in to ensure a continuous timeline. The MonthlyTotalAction endpoint (GET /module/reports/payments/total-per-month/all) offers monthly payment summaries split into two categories: payments with bills and payments without bills, also with missing months filled. All endpoints use the ReportsRepository for data fetching and return structured JSON responses suitable for charting libraries.

src/Action/Modules/Reports/Payments · high confidence

New payment settings endpoints for currency, types, and recurring payments

The payment settings module now exposes dedicated API endpoints to manage currency multipliers, payment types, and recurring payment configurations. Users can retrieve and update the global currency multiplier, as well as create, read, update, and delete payment types and recurring payment schedules (including day of month, amount, and description). The recurring payment creation and update logic now includes validation for required fields and ensures the referenced payment type exists before saving.

src/Action/Modules/Payments/Settings · high confidence

New payment tracking capabilities for income, monthly payments, debts, and product prices

Users can now manage four new types of financial records within the Payments module: income entries, monthly recurring payments (including bulk import), debts/owed amounts, and product prices. These features are exposed via new API endpoints (e.g., /module/payment/income, /module/payment/monthly) that allow creating, reading, updating, and deleting records, with monthly payments supporting import from JSON data and product prices displaying values converted to the home currency.

src/Action/Modules/Payments · high confidence

New private deployment and infrastructure management scripts

Added three new shell scripts to the private directory to streamline local development and deployment workflows. deploy.bash enables rsync-based code deployment to either a Raspberry Pi or a demo Hetzner host, handling file synchronization and container cache clearing. docker-compose.bash provides a reusable interface for running Docker Compose commands against specific hosts and architectures (ARM for Pi, AMD64 for demo). git-diff-last-tag-vs-now.bash generates a summary of changes since the last git tag, useful for release notes or changelog generation.

private · high confidence

New reports repository for payment summaries and historical owed money

A new ReportsRepository has been added to provide data for financial reporting features. It introduces methods to calculate monthly payment summaries (distinguishing between amounts with and without bills), fetch total payment amounts grouped by type, and retrieve historical records of money owed. This backend support enables the frontend to display charts and tables for monthly payments, payment types, and outstanding debts.

src/Repository/Modules/Reports · high confidence

New repository layer for schedules, calendars, and reminders

The application now uses dedicated Doctrine repositories to manage schedule data, introducing \MyScheduleCalendarRepository\, \MyScheduleReminderRepository\, and \MyScheduleRepository\. These components provide the backend persistence logic for the new schedule system, including specific methods to retrieve incoming schedules, identify those with unprocessed reminders, and fetch data for the dashboard widget.

src/Repository/Modules/Schedules · high confidence

New request, response, and utility service classes

Added three new service classes to the application: RequestService provides a static method to safely parse JSON request bodies, throwing an exception if the content is invalid; ResponseService handles CORS header injection (Access-Control-Allow-Origin, Methods, Headers) and determines whether incoming requests should be processed as standard BaseResponse JSON or bypassed for special handling (e.g., file downloads); and Utils offers helper functions for array manipulation (random selection, non-repeating value extraction) and type conversion (string-to-boolean, string-to-array parsing).

src/Services · high confidence

New savings report endpoint for monthly income and expense summaries

A new \SavingsAction\ controller has been added at \/module/reports/savings/all\ to provide data for savings charts. This endpoint aggregates monthly income (from \MyPaymentsIncomeRepository\) and expenses (from \ReportsRepository\) to calculate the net savings for each month, returning the results as a JSON list of value/label pairs suitable for charting.

src/Action/Modules/Reports · high confidence

New schedule, calendar, and reminder data models

The application now persists calendar data using new Doctrine entities: MyScheduleCalendar (managing calendar metadata like name and colors), MySchedule (representing individual events with title, body, time, and location), and MyScheduleReminder (handling per-event reminders with a unique constraint on schedule and date). All entities support soft deletion and are linked via one-to-many relationships, enabling the backend to store and retrieve schedule information for the front-end calendar view.

src/Entity/Modules/Schedules · high confidence

New schedules:send-reminders command sends notifications via Discord webhooks

A new console command, schedules:send-reminders, has been added to handle sending schedule reminders. The command retrieves pending reminders from the database, constructs notification payloads, and dispatches them through configured handlers. Currently, it supports sending messages via Discord webhooks using the DiscordService. After processing each reminder, the command marks the reminder as processed in the database to prevent duplicate notifications.

src/Command/Module/Schedules · high confidence

New settings endpoints for managing contact groups and types

This change introduces two new API controllers, GroupAction and TypeAction, under the /module/contacts/settings path, enabling users to create, read, update, and soft-delete contact groups and contact types via JSON endpoints. The GroupAction endpoint supports managing group names and colors, while the TypeAction endpoint handles type names and image paths (supporting both local file paths and URLs), including logic to update associated contacts when a type is modified.

src/Action/Modules/Contacts/Settings · high confidence

New shell service to read storage directory structure as JSON

Added \ShellAbstractService\ and \ShellTreeService\ to the backend, enabling the application to read the structure of a storage directory and return it as a JSON-formatted tree (including file sizes, absolute paths, and hidden files) via the \tree\ command-line utility. This capability allows the frontend to receive and display the detailed layout of stored files.

src/Services/Shell · high confidence

New storage file entity and polymorphic module association

Added the StorageFile entity to persist file metadata (path, name, module) in a new storage\_file table, and introduced the StorageFile2Module entity to link these files to any module entity via a pseudo-polymorphic relationship (storing related module ID and class) in a new storage\_file\_2\_module table.

src/Entity/Modules/Storage · high confidence

New storage file repository with polymorphic module associations

This change introduces the StorageFileRepository, which manages the new StorageFile entity and its polymorphic relationship with modules via the StorageFile2Module table. For users, this enables files to be linked to various module types (such as FILES and IMAGES) and ensures that file paths are correctly updated when directories are renamed or modules are moved. The repository also handles the cleanup of these associations when files are removed, ensuring data consistency across the storage system.

src/Repository/Modules/Storage · high confidence

New storage management endpoints for files and folders

This change introduces new API endpoints in the storage module to manage files and directories. Users can now rename, remove, and move files via the StorageFileAction, and create, rename, lock/unlock, and retrieve directory structures via the StorageFolderAction. The implementation includes validation for path safety, checks for locked resources to prevent modifications to restricted directories, and updates to database entities (StorageFile, FilesTags) to reflect file system changes. A new 'all' endpoint allows retrieving the complete tree structure of storage modules.

src/Action/Modules/Storage · high confidence

New structured DTOs for Settings modules (Dashboard, Finances, Lock, Notifications)

The Settings area now uses a set of new Data Transfer Objects to manage configuration data for Dashboard widgets, Finances (currencies), Module Locking, and Notifications. Users can now have their dashboard widget visibility preferences, financial currency settings (including multipliers and default flags), module lock states, and notification configurations (such as Discord webhooks) persisted and retrieved via these structured DTOs, replacing previous ad-hoc handling.

src/DTO/Settings · high confidence

New structured file upload service with validation and tagging support

The file upload logic in src/Services/Files/Upload has been replaced with a new service layer that centralizes configuration and enforces strict validation rules. Users can now upload profile pictures, images, videos, and general files, with specific constraints applied per type (e.g., profile pictures are limited to 2MB and do not allow tagging, while images and videos support multi-upload and tagging). A new configuration system (FileUploadConfigurator) defines allowed extensions and MIME types for each upload context, including support for CSV and XLSX files for monthly payment imports. The new FileUploadService handles the upload lifecycle, including pre-upload validation (size, extension, MIME type), post-move integrity checks, and automatic file tagging via the FilesTags entity. Temporary file handling is also managed by a dedicated service, ensuring safe storage and cleanup.

src/Services/Files/Upload · high confidence

New system repositories for resource locking and module management

Added LockedResourceRepository and ModuleRepository to handle system-level data access. LockedResourceRepository provides methods to check, add, and remove resource locks based on record, type, and target, including an optimized SQL statement builder for lock existence checks. ModuleRepository adds a helper to retrieve modules by name, with an option to include inactive modules.

src/Repository/System · high confidence

New system search and notification endpoints

The system module now exposes dedicated API endpoints for global search and notifications. The new SearchAction provides a unified search capability that scans storage files (including tag-based matching) and notes, while respecting module lock statuses to hide results from locked modules. The new NotificationAction retrieves incoming schedule information over the next 60 days, categorizing entries by urgency (info, warn, error, critical) based on the number of days remaining.

src/Action/Modules/System · high confidence

New upload configuration data structure

A new UploadConfigurationDTO has been introduced to define upload settings, including constraints such as maximum file size, allowed extensions and MIME types, multi-upload capability, and the ability to allow user naming and file tagging.

src/DTO/Internal · high confidence

Notes module: CRUD operations, locking, and category management

The Notes module now supports full create, read, update, and delete operations for notes and their categories via new API endpoints. Users can manage notes with titles and bodies, assign them to nested categories (up to 4 levels deep), and toggle resource locking to control visibility. The system enforces validation rules, such as preventing duplicate category names within the same parent and disallowing circular parent references, ensuring data integrity during note and category management.

src/Action/Modules/Notes · high confidence

Notification settings configuration endpoint

A new API endpoint is available at /module/system/settings/notifications/config to manage notification preferences. Users can retrieve the current notification configuration via a GET request to /all, which returns a list of available notification types with their active status and values, or update these settings via a PATCH request to the root path by providing a JSON body containing the new configuration array.

src/Action/Modules/System/Settings/Notification · high confidence

Removals

Removal of My Dashboard Twig templates

The dashboard layout template (dashboard.html.twig) and the settings placeholder (settings.twig) for the My Dashboard module have been removed from the codebase. This eliminates the previous Twig-based rendering for the main dashboard view and its associated settings configuration.

templates/modules/my-dashboard · high confidence

Removal of My-Achievements and My-Job Afterhours templates

The Twig templates for the My-Achievements module (index.html.twig) and the My-Job Afterhours section (afterhours.html.twig) have been deleted. This removes the user-facing views that previously displayed achievement tables, the form to add achievements, the tables for all/spent afterhours, the summary of remaining afterhours per goal, and the form to add or spend afterhours.

templates/modules/my-job · high confidence

Removal of MyJobAfterhoursController

The MyJobAfterhoursController has been deleted from the application. This removes the dedicated controller handling the 'my-job/afterhours' route and its associated update and remove actions, indicating that this functionality is no longer served by this specific component.

src/Controller/Modules/Job · high confidence

Removal of legacy DashboardController

The legacy DashboardController has been removed from the application. This file previously handled the rendering of the main dashboard view and fetched data for car schedules, goals, and goal payments via the Application utility class. Its deletion indicates that dashboard functionality has been migrated to other controllers or components within the Modules/Dashboard area.

src/Controller/Modules/Dashboard · high confidence

Removal of legacy Goals module controllers

The GoalsListController, GoalsPaymentsController, and MyGoalsSettingsController files have been deleted from the application. This removes the backend endpoints and logic previously used to manage the list, payments, and settings for the 'My Goals' module, indicating that this legacy functionality is no longer supported or has been replaced by other components.

src/Controller/Modules/Goals · high confidence

Removal of legacy My Notes controllers

The \MyNotesCategoriesController\ and \MyNotesController\ files have been deleted from the application. This removes the legacy controller logic that previously handled the rendering and submission of the My Notes settings form, as well as the creation, updating, and deletion of notes and categories via the \/my-notes/\*\ routes.

src/Controller/Modules/Notes · high confidence

Removal of legacy MyPayments and MyShopping Twig templates

The legacy Twig templates for the MyPayments and MyShopping modules have been removed. This includes the main view pages (monthly.html.twig, products.html.twig, settings.html.twig, plans.html.twig) and their associated component templates (payments.table.html.twig, products.table.html.twig, types-settings.table.html.twig, table.html.twig). These files, which previously rendered payment tables, product price lists, shopping plans, and settings forms, are no longer present in the codebase.

templates/modules/my-payments · high confidence

Removal of legacy Travel Ideas controller

The \MyTravelsIdeasController\ has been deleted, removing the legacy PHP controller that previously handled the display, creation, update, and removal of travel ideas via direct repository calls. This change eliminates the old routing and form-handling logic for this module, indicating that the functionality has been migrated or replaced by other components.

src/Controller/Modules/Travels · high confidence

Removal of legacy Twig extensions

The \src/Twig\ directory has been reorganized by removing several legacy Twig extension classes: \Calculations\, \CssClasses\, \GlobalVariables\, \RecursiveMenuElements\, \TemplatesLoader\, and \Utils\. This removes associated template functions such as \calculateHomeProductPrice\, \getClassForAchievementType\, \getMyNotesCategories\, \unsetChildren\, \getBaseTemplate\, and \keepMenuOpen\ from the Twig environment.

src/Twig · high confidence

Removal of legacy Twig template files

The \base.html.twig\, \blank.html.twig\, \sidebar.twig\, \topbar.twig\, and \all-interface-examples.twig\ template files have been deleted from the application. This removes the previous HTML structure, page loader, sidebar menu components, and demo interface examples that were previously rendered by these templates.

templates · high confidence

Removal of legacy Twig-based flash message component

The \messages.twig\ template, which previously rendered flash messages via a Twig loop and initialized Bootstrap notifications through inline JavaScript, has been deleted. This change removes the server-side rendered message display logic in favor of the frontend TypeScript scripts and AJAX handling introduced in recent commits, which now manage form validation and message display directly in the browser.

templates/page-elements/components/messages · high confidence

Removal of legacy contacts and groups table templates

The legacy Twig templates for the contacts table (contacts-table.html.twig) and groups settings table (groups-settings.table.html.twig) have been removed from the my-contacts module. These files previously rendered the HTML structure for displaying and editing contact records and group associations; their deletion indicates a shift away from this specific rendering approach, likely as part of the cleanup and renaming from 'contacts2' to 'contacts'.

templates/modules/my-contacts/components · high confidence

Removal of legacy demo page templates

The standalone Twig templates for the demo pages (including 404, 500, basic-table, calendar, charts, chat, compose, dashboard, and datatable) have been removed from the \templates/demo-pages\ directory. This change eliminates the previous self-contained HTML structures for these views, indicating a shift in how these demo interfaces are rendered or integrated within the application.

templates/demo-pages · high confidence

Removal of legacy form event logic and utilities

The \DatalistLogicOverride\ class and the \Utils\ helper class within \src/Form/Events\ have been removed. These components previously handled custom data modification for Symfony form events, specifically allowing users to enter values outside a predefined list and managing data transformation for objects and arrays. Their deletion indicates that this custom override logic is no longer required for the application's form handling.

src/Form/Events · high confidence

Removal of legacy form types

The legacy DatalistType and FontawesomepickerType form types have been removed from the application. These custom wrappers around Symfony's ChoiceType and TextType are no longer available for use in forms.

src/Form/Type · high confidence

Removal of legacy password management controllers

The legacy controllers for managing user passwords and password groups (MyPasswordsController and MyPasswordsGroupsController) have been removed from the application. This change eliminates the previous implementation that handled password display, creation, updates, and retrieval via AJAX, as well as the management of password groups through a dedicated settings page. Users will no longer interact with these specific controller endpoints, indicating a shift to a different architectural approach for handling password-related functionality.

src/Controller/Modules/Passwords · high confidence

Removal of legacy sidebar header and menu templates

The \header.twig\ and \menu.twig\ files within the sidebar component have been deleted. This removes the previous implementation of the sidebar logo area (including the dashboard link and mobile toggle) and the static menu structure that included hardcoded links for Dashboard, Goals, Notes, Contacts, Passwords, Achievements, Car, Travels, Payments, Shopping, and Job. Users will no longer see this specific sidebar layout.

templates/page-elements/components/sidebar · high confidence

Removal of legacy sidebar menu node templates

The sidebar menu node templates for Achievements, Goals, Integrations, My Car, My Contacts, My Job, My Passwords, My Payments, My Shopping, My Travels, Notes, and Notes Categories have been deleted. This removes the specific Twig definitions that previously rendered these items in the application's sidebar navigation.

templates/page-elements/components/sidebar/menu-nodes · high confidence

Removal of legacy topbar components

The static topbar components for emails, notifications, search, sidebar toggle, and user profile have been removed from the templates. This cleanup eliminates the hardcoded UI elements and Twig includes that previously rendered these sections, indicating a shift away from this specific template structure for the topbar.

templates/page-elements/components/topbar · high confidence

Removal of legacy user settings template

The \templates/page-elements/user/settings.html.twig\ file has been deleted. This template previously rendered the user profile settings page, including forms for changing the avatar, password, and nickname, as well as an avatar preview section. Its removal indicates that this specific UI component is no longer used or has been replaced by a different implementation.

templates/page-elements/user · high confidence

Removal of the Travel Ideas module templates

The Twig templates for the Travel Ideas feature have been deleted. Specifically, \templates/modules/my-travels/ideas.html.twig\ (the main page view) and \templates/modules/my-travels/components/ideas.table.html.twig\ (the table row component) are no longer present in the codebase, meaning the user interface for viewing and adding travel ideas is removed.

templates/modules/my-travels · high confidence

Removal of the plus-icon widget template

The Twig template for the plus-icon widget has been removed from the codebase. This eliminates the specific UI component previously rendered by this file, which displayed a circular plus icon intended to trigger a modal action.

templates/page-elements/components/widgets · high confidence

Removed FOSUserBundle layout template

The default layout template for the FOSUserBundle has been deleted. This removes the shared HTML structure, including the CSS/JS asset links, the loading spinner animation, and the content block definition that previously wrapped FOSUserBundle pages.

templates/bundles/FOSUserBundle · high confidence

Removed My Goals Twig templates

The Twig templates for the My Goals module (list, payments, and settings pages) have been deleted from the codebase. This removes the server-side rendered views for displaying goal lists, payment progress, and goal configuration forms.

templates/modules/my-goals · high confidence

Removed MyCar schedule form types

The MyCarSchedule and MyCarScheduleType form classes in the Car module have been removed. This eliminates the ability to create or manage car schedules through these specific Symfony form types, which previously handled fields for name, date, information, and schedule type selection.

src/Form/Modules/Car · high confidence

Removed MyJob Afterhours table template

The Twig template for the MyJob Afterhours table (afterhours.table.html.twig) has been removed from the project. This component previously rendered the data table for afterhours records, including column headers, row data, and action icons for editing and deletion. Its removal indicates that the rendering logic for this specific table has been moved or replaced elsewhere in the application.

templates/modules/my-job/components · high confidence

Removed MyJobAfterhours form type

The MyJobAfterhoursType form class has been removed from the application. This form previously allowed users to log after-hours work by specifying a date, description, minutes, goal, and type, including logic to handle goal selection via a DataList or text input. Its removal indicates that the ability to submit after-hours job entries through this specific form interface is no longer available.

src/Form/Modules/Job · high confidence

Removed MyShoppingPlansController

The MyShoppingPlansController, which previously handled the display, update, and removal of shopping plans via routes like /my-shopping/plans, has been deleted from the application. This change removes the specific controller logic for managing the 'My Shopping Plans' module, indicating that this functionality has been migrated or replaced by other components within the system.

src/Controller/Modules/Shopping · high confidence

Removed SCSS specification files

Deleted the entire \src/scss/spec\ directory, including all component styles (sidebar, topbar, forms, etc.), settings (colors, breakpoints, fonts), utility helpers (flex, layout, border), and screen-specific styles (chat, email).

src/scss/spec · high confidence

Removed legacy Achievement form type class

The \AchievementType\ class, which previously defined the Symfony form structure for creating and editing achievements (including fields for Name, Description, Type, and a submit button), has been deleted from the codebase. This removal indicates that the form handling logic for achievements has been refactored or migrated to a different implementation, and this specific legacy form definition is no longer used.

src/Form/Modules/Achievements · high confidence

Removed legacy AchievementController

The legacy AchievementController has been deleted from the codebase. This removal eliminates the previous implementation of the achievements module's controller logic, which previously handled displaying achievements, updating records, and removing achievements via direct repository calls and form handling.

src/Controller/Modules/Achievements · high confidence

Removed legacy MyCar template files

The template files for the MyCar module have been deleted. This includes the main view (my-car.html.twig), the settings view (settings.html.twig), and the associated component templates (table.html.twig and schedule-types-settings.table.html.twig). These files previously rendered the car schedule data table with inline date-based coloring logic and the schedule type management form.

templates/modules/my-car · high confidence

Removed legacy MyContacts controllers

The legacy controllers for the MyContacts module (MyContactsController, MyContactsGroupsController, and MyContactsSettingsController) have been deleted. This removes the previous implementation of the My Contacts and My Contacts Settings pages, including their associated routes and AJAX handling logic, as part of a broader refactor to clean up old contact logic.

src/Controller/Modules/Contacts · high confidence

Removed legacy MyGoals component templates

The Twig template files for the MyGoals module components have been deleted. This removes the UI definitions for the checklist, goals payments table, goals settings table, modal dialog, parent task goal button, individual payment display, and subgoals settings table. Users will no longer see these specific interface elements rendered by these templates.

templates/modules/my-goals/components · high confidence

Removed legacy MyPayments form types

The legacy form type classes for the MyPayments module (MyPaymentsMonthlyType, MyPaymentsProductsType, MyPaymentsSettingsCurrencyMultiplierType, and MyPaymentsTypesType) have been removed from the codebase. This cleanup eliminates the old Symfony form definitions that previously handled monthly payment entries, product payments, currency multiplier settings, and payment type configurations, indicating these specific UI components are no longer supported or have been replaced by other implementations.

src/Form/Modules/Payments · high confidence

Removed legacy MyTravelsIdeas form type

The MyTravelsIdeasType form class, which previously handled travel idea submissions with dynamic category selection via DatalistType, has been removed from the application. This change eliminates the legacy form logic that allowed users to pick from a predefined list of categories or type a new one, along with associated fields for location, country, image, and map links.

src/Form/Modules/Travels · high confidence

Removed legacy Twig templates for My Passwords module

The legacy Twig templates for the My Passwords module have been removed. This includes the main view templates for managing passwords and credential groups, as well as the specific table components used to render lists of passwords and groups. Users will no longer see these specific UI structures, indicating a shift to a different rendering approach or component library for this module.

templates/modules/my-passwords · high confidence

Removed legacy Twig templates for contacts and settings

The legacy Twig templates for the main contacts view (my-contacts.html.twig) and the contact groups settings page (settings.html.twig) have been deleted. These files previously handled the rendering of the contact add/remove forms and the contact group management interface respectively. Their removal indicates that the UI for these features has been migrated to a different implementation, likely the new TypeScript/AJAX-based approach mentioned in the commit history.

templates/modules/my-contacts · high confidence

Removed legacy compiled frontend assets

The large, pre-compiled \app.css\ and \app.js\ bundles, along with several static image and CSS files, have been removed from the \public/assets\ directory. This cleanup reduces the size of the production frontend package and removes outdated resources that are no longer part of the active build pipeline.

public/assets · high confidence

Removed legacy contact form types

The legacy form types for managing individual contacts and contact groups (MyContactsType and MyContactsGroupsType) have been removed from the application. This cleanup eliminates the previous logic for creating and editing contact entries and their associated groups, aligning with the broader renaming of the contacts module.

src/Form/Modules/Contacts · high confidence

Removed legacy controller utility classes

Deleted the \GeneralMessagesController\, \Ajax\, \Application\, \Forms\, and \Repositories\ classes from the \src/Controller/Utils\ directory. These files served as legacy containers for static message constants, stubbed AJAX endpoints, and dependency-injection wrappers for repositories and forms, which are no longer used in the application.

src/Controller/Utils · high confidence

Removed legacy dashboard widget templates

The dashboard no longer renders the 'Incoming car schedules', 'Goals payments progress', and 'Goals progress' widgets, as their corresponding Twig templates have been deleted. Users will no longer see these specific summary views on their main dashboard until replacement components are introduced.

templates/modules/my-dashboard/widgets · high confidence

Removed legacy frontend asset scripts and libraries

The frontend asset bundle in src/assets/scripts has been significantly reduced by deleting numerous legacy JavaScript files and libraries. This includes the removal of the bootstrap-notify plugin, jQuery UI (including touch-punch), fullcalendar, Google Maps integration, masonry layout, and various UI modules such as charts, datepickers, datatables, and email/chat interfaces. The main entry point (index.js) has also been deleted, indicating a major restructuring or migration of the frontend architecture away from these specific bundled scripts.

src/assets/scripts · high confidence

Removed legacy icon picker data and JS

The legacy icon picker library (furcan-iconpicker) has been removed. The static icon data file (iconpicker-1.0.0.json) containing hundreds of FontAwesome icon definitions has been deleted, and the associated JavaScript file (all.js) has been removed. This cleanup likely accompanies the recent updates to the FontAwesome picker implementation.

public/assets\ · high confidence_

Removed legacy password form types

The legacy form types for managing individual passwords and password groups (MyPasswordsType and MyPasswordsGroupsType) have been removed from the application. This cleanup eliminates the previous manual form definitions for creating and editing password entries and their associated groups, aligning with the broader removal of legacy todo and password forms.

src/Form/Modules/Passwords · high confidence

Removed legacy user form types

The legacy form types for managing user avatars, nicknames, and passwords have been removed from the application. This change eliminates the dedicated form classes (UserAvatarType, UserNicknameType, UserPasswordType) that previously handled these specific user profile fields, simplifying the form structure by removing these individual components.

src/Form/Modules/Notes, src/Form/User · high confidence

Removed obsolete Goals and Shopping form types

The MyGoalsPaymentsType, MyGoalsType, MySubgoalsType, and MyShoppingPlansType form classes have been removed from the application. This eliminates the legacy form definitions for managing goal payments, general goals, subgoals, and shopping plans, simplifying the form module structure.

src/Form/Modules/Goals · high confidence

Removed obsolete and unused controller classes

The AdminController, AppController, MyCarController, MyCarSettingsController, and UtilsController have been deleted from the application. This removes the generic admin page router, the main login redirect, the MyCar module's display/update/remove endpoints, the MyCar settings management endpoints, and a static base64 utility method, effectively cleaning up legacy or unused backend routing and logic.

src/Controller · high confidence

Removed recursive nested menu Twig template

The \recursive-nested-menu-element.twig\ template, which previously handled the rendering of recursive sidebar menu items with category-based links and icons, has been deleted from the codebase. This change removes the specific Twig logic responsible for generating nested list structures for the sidebar navigation components.

templates/page-elements/components/sidebar/components · high confidence

Architecture

Centralize system configuration, locking, and security logic into new service classes

This change introduces three new service classes in the System module to consolidate core application logic. EnvReader provides a unified interface for accessing environment variables and parsing database credentials, replacing direct $\_ENV usage. LockedResourceService manages resource locking states (entities, directories, modules) and enforces access rules based on system and module lock settings. SecurityService encapsulates password validation logic using the encoder factory. These services replace scattered controller and utility code, providing a cleaner, more maintainable foundation for system-level operations.

src/Services/System · high confidence

Behavioural changes

1 commit (0 fixes) modifying (repo-wide)

A change to existing behaviour in (repo-wide) — 1 commit, 161 files: “♻️ Rectorize: annotations to attrs, prepare for further symfony updates”. Also in this area: JWT authentication logic restored and refactored.

src/Security/UserChecker · low confidence · unverified

1 commit (0 fixes) modifying (repo-wide)

A change to existing behaviour in (repo-wide) — 1 commit, 161 files: “♻️ Rectorize: annotations to attrs, prepare for further symfony updates”. Also in this area: New CLI commands for JWT token management and a locked resource response.

(repo-wide) · low confidence · unverified

2 commits (0 fixes) modifying src/Services

A change to existing behaviour in src/Services — 2 commits, 27 files: “🐛 Profile pic upload crashes”; “♻️ Rectorize: annotations to attrs, prepare for further symfony updates”. Also in this area: Extracted business logic for contacts and notes into dedicated services.

src/Services/Chart, src/Services/Module/Contacts, src/Services/Module/Health, src/Services/External · medium confidence · unverified

Added custom Nginx configuration for optimized static file serving and PHP-FPM integration

A new Nginx configuration file has been introduced to replace default settings, enabling HTTP/2, gzip compression for various content types, and specific performance optimizations such as tuned buffer sizes and connection timeouts. The configuration sets up the server to serve static files from /application/public and proxies PHP requests to the pms-php-fpm service on port 9000, ensuring efficient handling of dynamic content and static assets.

docker/nginx · high confidence

Added module provider for demo data generation

A new ModuleProvider class has been introduced in the system data fixtures to define the list of supported modules (Issues and Goals) used for populating demo data. This change ensures that the demo data generators include the necessary module entries, addressing a previous omission in the test fixtures.

src/DataFixtures/Providers/System · high confidence

Automated recurring payments and scheduled backups via cron

The system now includes automated cron jobs for recurring payments and data protection. A new 'pms' crontab entry executes the 'cron:set-recurring-payments' command hourly. Additionally, the 'pms-pi' crontab schedules daily tasks: sending schedule reminders at midnight, creating configuration backups at 01:00, performing database backups at 01:15, and executing file backups every third day at 02:00.

docker/php-fpm/crontab · high confidence

Automatic hydration and synchronization of storage file associations

A new Doctrine event subscriber has been introduced to automatically manage the relationship between entities and their associated storage files. This change ensures that when an entity is loaded, its related storage files are fetched and set, and during flush operations, the many-to-many relations are correctly synchronized in the database. This resolves issues where new entities failed to hydrate storage files or where unlinking files did not properly update the association.

src/Listeners/Entity · high confidence

Centralized settings management for dashboard, finances, notifications, and module locks

The application now uses a dedicated service layer in src/Services/Settings to manage system configuration, replacing previous ad-hoc handling. Users can now persist and retrieve settings for dashboard widget visibility, financial currencies (including default currency selection and validation), notification configurations, and module access locks. This change ensures that settings are correctly loaded from and saved to the database, fixes issues where new settings were incorrectly created instead of updating existing ones, and provides a unified mechanism for validating unique values like currency names.

src/Services/Settings · high confidence

Contacts module refactored with soft-delete support and new grouping entities

The Contacts module has been restructured to introduce a new MyContact entity that supports soft deletion and stores contact details as JSON, alongside a new MyContactGroup entity for organizing contacts. The previous MyContactsGroups entity has been renamed to MyContactType, now includes an image path field, and also implements soft-delete capabilities. These changes enable better data integrity, logical deletion of records, and improved organization of contact types and groups within the application.

src/Entity/Modules/Contacts · high confidence

Contacts module repository layer refactored and renamed

The repository layer for the Contacts module has been restructured to align with updated entity naming and Doctrine standards. Old repositories (\MyContactsRepository\, \MyContactsGroupsRepository\) using the legacy \RegistryInterface\ have been removed and replaced with new, strongly-typed repositories (\MyContactRepository\, \MyContactGroupRepository\, \MyContactTypeRepository\) that extend \ServiceEntityRepository\ with \ManagerRegistry\. This change introduces specific data access capabilities, including soft-delete filtering (e.g., \findAllNotDeleted\), UUID-based lookups, and JSON-based contact type searches within \MyContactRepository\, while also adding a \saveEntity\ method to handle entity persistence and reconstruction from form data.

src/Repository/Modules/Contacts · high confidence

Dashboard now aggregates widget data with visibility and lock-state checks

The dashboard endpoint now fetches and returns data for four specific widgets: Goal Payments, Goal Progress, Issues, and Schedules. This data is only included if the corresponding module is accessible (checked via DashboardService) and the widget is enabled. Additionally, the response includes a lock state for each widget, indicating whether the associated module is locked by system settings, allowing the frontend to display appropriate UI states.

src/Action/Modules/Dashboard · high confidence

Dashboard widgets now respect module access locks

The new DashboardService enforces that dashboard widgets only return data when their underlying module is accessible to the user. By checking the module's lock status via LockedResourceService, the system prevents users from viewing widget content for modules they do not have permission to access, ensuring that visibility settings are properly gated by access rights.

src/Services/Module/Dashboard · high confidence

Database schema migrations for new modules and structural refactors

This update applies a series of database migrations that introduce several new features and restructure existing data models. New capabilities include a Job Holidays module (tracking pools and settings), a unified Scheduling system (replacing the previous car-specific logic with a generic calendar and schedule type structure), and a new Issue tracking module with progress and contact associations. The database schema is also significantly refactored: numerous tables are renamed to singular forms (e.g., \my\_goals\ to \my\_goal\), the Goals and Subgoals tables are migrated into a generic Todo system, and the Owed Payments amount field is changed from integer to float to support precise currency values. Additionally, contact management is overhauled with new groups and types, and recurring payments are adjusted to use a specific day-of-month field instead of a full date.

src/Migrations · high confidence

Goals module repository cleanup and dashboard data access

The MyGoalsRepository and MyGoalsSubgoalsRepository classes have been removed, eliminating legacy direct database queries for checking subgoal completion and updating goal status. The MyGoalsPaymentsRepository has been updated to use the modern ManagerRegistry interface and now includes new methods, getGoalsPaymentsForDashboard and getAllNotDeleted, to explicitly fetch payment data for the dashboard and retrieve non-deleted records respectively.

src/Repository/Modules/Goals · high confidence

Introduce PHP 8 AttributeReaderService for route and class attribute inspection

A new AttributeReaderService has been added to handle reading and checking PHP 8 attributes on classes and methods. This service replaces the previous annotation-based approach, allowing the system to inspect specific attributes on route methods (via URI matching) and class definitions. It provides methods to check for the presence of attributes and retrieve them by name, supporting a more modern and native PHP attribute syntax for configuration and metadata.

src/Services/Attribute · high confidence

Introduce dedicated routing services for URL matching and URI filtering

This change introduces two new services in the routing layer to centralize URL handling logic. The new UrlMatcherService provides methods to resolve controllers and routes from URLs, specifically handling query parameters that previously caused the underlying Symfony matcher to crash, and suppressing noisy warnings for standard OPTIONS requests. Additionally, the new UrlService adds a utility to identify and exclude development and system URIs (such as the profiler, web debug toolbar, and fragments) from processing, addressing issues where these internal routes were incorrectly treated as inaccessible.

src/Services/Routing · high confidence

Introduce new validation service architecture

The validation layer in src/Services/Validation has been restructured with new services to handle different validation scenarios. A new ConstraintValidationService processes Symfony validator violations into a ValidationResultDto, while a new EntityValidatorService manages entity-specific validation by mapping entities to dedicated validators (currently for MyJobHolidays and MyRecurringPaymentMonthly) and supporting create/update actions. Additionally, a new ValidationService provides a static utility for JSON string validation, and an AbstractValidator base class establishes the pattern for module-specific validators.

src/Services/Validation · high confidence

Introduce request-scoped system lock state storage

Added a new \RequestSessionStorage\ class in the storage service layer to manage system lock state during frontend requests. This class provides static properties (\IS\_SYSTEM\_LOCKED\ and \IS\_TOGGLE\_LOCK\_CALL\) to store lock-related data for the current request lifecycle, addressing issues where standard session storage was not functioning correctly with frontend requests.

src/Services/Storage · high confidence

Introduce structured configuration loaders for system and security settings

The application now uses dedicated configuration loader classes to manage specific settings, replacing ad-hoc handling. A new \ConfigLoaderSecurity\ class exposes restricted IP addresses via a \getRestrictedIps\ method, parsing the string-based environment variable into an array. Additionally, a \ConfigLoaderSystem\ class provides access to the system's 'from' email address. These loaders extend a new \AbstractConfigLoader\ base class, establishing a standardized pattern for loading these specific configuration values.

src/Services/ConfigLoaders · high confidence

Introduce system resource locking and secure file access endpoints

The system now supports locking and unlocking resources via a new toggle endpoint that hides locked items from users unless they provide a valid lock password, enhancing data privacy. Additionally, file downloads are now routed through a dedicated action that validates file paths against allowed directories to prevent directory traversal attacks, ensuring that only permitted files are served. A new registration endpoint allows creating the first user account with both login and lock passwords, while JWT token refresh logic is centralized in a listener triggered by a specific security route.

src/Action/System · high confidence

Introduces backend enums for file uploads, storage modules, and user permissions

This change adds several new PHP enums to the backend to support file management and access control features. UploadStatusEnum defines success and error states for file uploads, while UploadedFileSourceEnum categorizes sources such as profile images and storage modules. StorageModuleEnum lists available storage types (videos, images, files), and RelatableModuleEnum maps user-specific contexts like My Issues and My Goals. Additionally, UserModuleRightEnum establishes granular permission flags for accessing various modules, including the new Health module, ensuring these rights are synchronized with the frontend.

src/Enum · high confidence

JWT authentication logic restored and refactored

The security module now includes a new LexitBundleJwtTokenAuthenticator that handles JWT token extraction, validation, and expiration checks, replacing the previous broken mechanism. A new UriAuthenticator class allows specific URIs to be excluded from authentication based on regex patterns, while a stub LoginUserChecker has been added to satisfy Symfony's user checker interface requirements.

src/Security · high confidence

JWT tokens now include user profile, rights, and system lock status

The authentication flow has been updated so that generated JWT tokens now carry additional user context. When a token is created, it includes the user's email, username, ID, nickname, and the public path to their profile picture (defaulting to a dummy image if none is uploaded). It also embeds the user's current rights/permissions and the current system lock state, allowing the frontend to make immediate decisions about access and UI state without extra API calls.

src/Listeners/Bundles · high confidence

Migrate authentication to JWT and restructure Symfony configuration

The application replaces the FOSUserBundle with LexikJWTAuthenticationBundle for authentication, removing legacy user management and web server bundles while enabling JWT-based login and registration. Configuration is updated for Symfony 5.4, introducing environment-driven settings for restricted IPs, system email, and JWT token lifetime, alongside new service definitions for notifier proxy logging and external IO bridges. Legacy routing and test service configurations are cleaned up, and a development debug route is added for backend testing.

config · high confidence

MyGoalsPayments entity now supports soft deletion and structured frontend data export

The MyGoalsPayments entity has been updated to implement SoftDeletableEntityInterface, enabling cascade soft delete logic for these records. Additionally, the deadline and collectionStartDate fields are now mapped as date types with setters that automatically parse string inputs into DateTime objects, and a new asFrontendData method has been added to provide a standardized array of goal payment details (including start/end dates, goal amount, and collected amount) for dashboard consumption.

src/Entity/Modules/Goals · high confidence

MyTravelsIdeas entity implements soft-delete and standardizes interface methods

The MyTravelsIdeas entity now implements SoftDeletableEntityInterface and EntityInterface, enabling cascade soft-delete logic for travel ideas. Additionally, the getter method for the deleted status has been renamed from getDeleted to isDeleted to align with the new interface contract.

src/Entity/Modules/Travels · high confidence

New API endpoints for managing achievements

The system now exposes a dedicated REST API for handling achievements, replacing the previous controller implementation. Users can create, update, and retrieve achievements via POST, PATCH, and GET requests to /module/achievements. The API supports retrieving all achievements grouped by difficulty type (Hardcore, Hard, Medium, Simple) and allows for soft-deletion of records. This change introduces a new \AchievementAction\ class that handles these operations using the \AchievementRepository\ and \EntityManager\, ensuring data integrity through validation of required fields like name and type.

src/Action/Modules/Achievements · high confidence

New JWT-based authentication and module access control

The security service layer has been replaced with a new implementation centered on JWT tokens. JwtAuthenticationService now handles token extraction, validation, and refresh logic, while JwtUserRightsHandler dynamically calculates user permissions based on module lock states, ensuring that access rights (such as for storage, goals, or health modules) are accurately reflected in the token payload. Additionally, PasswordHashingService has been introduced to manage password encoding using Symfony's password hasher, supporting the new registration and authentication flows.

src/Services/Security · high confidence

New entities for file tagging and settings; User entity refactored for native Symfony authentication

The system introduces a new FilesTags entity to support tagging files by full path, and a Setting entity to store configuration values including dashboard widget visibility and lock states. The existing User entity has been significantly refactored to remove the dependency on the FOSUserBundle, implementing Symfony's native UserInterface and PasswordAuthenticatedUserInterface instead. This change adds explicit fields for username, email, roles, and a new lockPassword feature, enabling the application to handle its own authentication and user management logic directly.

src/Entity · high confidence

New exception classes for account status, file uploads, and missing data

Added three new exception classes to the application's exception hierarchy: DeletedUserException extends Symfony's AccountStatusException to handle deleted user scenarios; UploadValidationException extends the base Exception to indicate issues with uploaded files; and MissingDataException includes a configurable 'front' flag to distinguish between frontend and backend error handling contexts.

src/Exception · high confidence

New exception listener for structured error responses

A new ExceptionListener has been added to handle application exceptions by mapping them to specific HTTP responses. NotFoundHttpException and specific MissingDataException cases now return a 400 Bad Request response with the exception message, while other exceptions return a 500 Internal Server Error. Additionally, exceptions containing the message 'Full authentication is required to access this resource.' are excluded from logging to reduce noise.

src/Listeners/Exception · high confidence

New repository layer for MyTodo and MyTodoElement entities

The application now uses dedicated Doctrine repositories (MyTodoRepository and MyTodoElementRepository) to manage todo data, replacing previous direct or legacy access patterns. MyTodoRepository provides specific methods to fetch todos by module name (with optional dashboard filtering), retrieve all todos while respecting soft-delete states, and check if all elements within a specific todo are completed. This change centralizes data access logic for the MyTodo module.

src/Repository/Modules/Todo · high confidence

New repository layer for the MyIssue module

The Issues module now includes dedicated Doctrine repositories for MyIssue, MyIssueContact, and MyIssueProgress, replacing legacy repository calls. MyIssueRepository introduces specific query methods to filter issues by deletion status, resolution state, and dashboard visibility, enabling the system to correctly display pending issues and manage soft-deletable records.

src/Repository/Modules/Issues · high confidence

New response listeners enforce JSON structure and refresh JWT tokens

Three new event subscribers in the response layer now standardize API responses and manage authentication state. FrontResponseListener ensures all frontend responses return a 200 status code with CORS headers. JwtTokenResponseListener automatically refreshes JWT tokens in successful API responses and normalizes initial authentication success responses into the standard JSON format. ResponseValidityListener validates that all JSON responses contain the required BaseResponse fields, returning an internal server error if the structure is invalid or if non-JSON responses are detected.

src/Listeners/Response · high confidence

New structured data providers for shop and product fixtures

Added new fixture provider classes to organize test data into logical groups. The \Shops\ provider defines supermarket and domestic shop names, while the \Products\ namespace now includes \Domestic\ (chemicals, personal care, other), \ExpensiveProducts\ (high-value items with price ranges), and \Food\ (categorized by vegetables, fruits, meat, etc.). These providers replace or supplement previous fixture structures by offering grouped constants and aggregated lists for easier reference in data seeding.

src/DataFixtures/Providers/Business, src/DataFixtures/Providers/Products · high confidence

New validation rules for job holidays and recurring payments

Added dedicated validators for the Job and Payments modules to enforce specific business constraints. The MyJobHolidaysValidator now checks that days spent are greater than zero and do not exceed the available pool for the year, accounting for updates to existing records. The MyRecurringPaymentsValidator ensures that the day of the month for recurring payments falls within the allowed range defined by the entity's minimum and maximum constants.

src/Services/Validation/Validators/Modules/Job, src/Services/Validation/Validators/Modules/Payments · high confidence

Notes and Passwords entities adopt soft-delete pattern and naming conventions

The MyNotes, MyNotesCategories, MyPasswords, and MyPasswordsGroups entities now implement the SoftDeletableEntityInterface, enabling soft deletion capabilities for these records. This change includes renaming the deletion status accessor from getDeleted to isDeleted across all affected classes, updating the MyNotesCategories relationship mapping from 'setting' to 'category', and enforcing stricter parent-child validation to prevent circular references. Additionally, table names are explicitly defined (e.g., my\_note, my\_password) and PHP property naming is standardized to camelCase.

src/Entity/Modules/Notes · high confidence

Notes and Passwords entities adopt soft-delete pattern and naming conventions

The MyNotes, MyNotesCategories, MyPasswords, and MyPasswordsGroups entities now implement the SoftDeletableEntityInterface, enabling soft deletion capabilities for these records. This change includes renaming the deletion status accessor from getDeleted to isDeleted across all affected classes, updating the MyNotesCategories relationship mapping from 'setting' to 'category', and enforcing stricter parent-child validation to prevent circular references. Additionally, table names are explicitly defined (e.g., my\_note, my\_password) and PHP property naming is standardized to camelCase. Also in this area: 1 commit (0 fixes) modifying (repo-wide).

src/Entity/Modules/Passwords · low confidence · unverified

Notes and Passwords repositories modernized to use Doctrine QueryBuilder and ManagerRegistry

The repository layer for Notes and Passwords modules has been refactored to replace raw SQL queries with Doctrine's QueryBuilder and EntityManager, and to update dependency injection from the deprecated Symfony RegistryInterface to Doctrine's ManagerRegistry. This change improves code maintainability and type safety for users by ensuring that category trees, note searches, and password lookups are handled through the ORM, which also standardizes how soft-deleted records are filtered across these modules.

src/Repository/Modules/Notes · high confidence

Optimize public asset caching and migrate Symfony debug component

The public entry point now uses the updated Symfony ErrorHandler Debug component, replacing the deprecated Debug class to ensure compatibility with newer Symfony versions. Additionally, the .htaccess file has been updated to include HTTP caching headers for static assets (images, scripts, stylesheets) and HTML files, as well as enabling mod\_gzip compression, which improves page load performance for end users.

public · high confidence

Passwords module: new controller actions for managing passwords and groups

The Passwords module now exposes dedicated controller actions to manage password entries and their groups via the API. Users can create, update, and soft-delete individual passwords (including login, URL, description, and group association) and manage password groups (with duplicate name validation). These changes replace legacy controller/repository calls with a structured action-based approach, ensuring that password data is properly persisted and that group names remain unique.

src/Action/Modules/Passwords · high confidence

Payments module entities refactored and expanded with new income, bills, and owed money tracking

The payment tracking entities have been restructured to support a more granular view of personal finances. New entities have been introduced: MyPaymentsIncome for recording income sources, MyPaymentsBills and MyPaymentsBillsItems for managing recurring bill schedules and their individual line items, and MyPaymentsOwed for tracking money owed to or by the user. Existing entities have been standardized by implementing the SoftDeletableEntityInterface and EntityInterface, ensuring consistent soft-delete behavior across the module. The MyRecurringPaymentMonthly entity has been repurposed from a generic contact model to specifically handle recurring payment schedules with validation interfaces, while MyPaymentsSettings now defines specific configuration types for payment and currency handling.

src/Entity/Modules/Payments · high confidence

Payments module repository modernization and income calculation logic

The Payments module repositories have been migrated from the deprecated Symfony Doctrine Registry to the standard Doctrine ManagerRegistry, ensuring compatibility with current framework standards. New repository classes have been introduced for bills, bill items, income, owed amounts, and recurring monthly payments to support the new MyReports and MyPaymentsOwed features. Specifically, the income repository now provides a method to sum income amounts by year and month, which is used to correctly calculate savings based on income inputs. Additionally, the monthly payments repository has been refactored to optimize loading times by grouping payments by year and providing unique dates for income alignment, while legacy controllers and unused repository methods have been removed.

src/Repository/Modules/Payments · high confidence

Refactored Job module repositories and introduced new holiday tracking capabilities

The Job module's data access layer has been significantly restructured. New repositories for MyJobHolidaysPool and MyJobHolidays have been added to support tracking and spending of job-related holidays, including logic to calculate remaining days per calendar year. The existing MyJobAfterhoursRepository was refactored to replace the deprecated Symfony RegistryInterface with Doctrine's ManagerRegistry, and its query logic was simplified to return distinct goal names rather than complex time summaries, while adding new methods for filtering by type and finding entities by ID. Additionally, a new MyJobSettingsRepository was introduced.

src/Repository/Modules/Job · high confidence

Refactored custom exception classes for validation and security

The application's exception handling has been updated by introducing new specific exception classes while removing obsolete ones. A new \ExceptionValueNotAllowed\ class has been added to handle validation errors, specifically distinguishing between numeric values that must be higher than zero and string values that must not be empty. Additionally, a \SecurityException\ class has been introduced to represent security-related errors. The previous \ExceptionRepository\ class, which provided a generic message for missing properties or data in repository AJAX CRUD operations, has been removed.

src/Services/Exceptions · high confidence

Refactored storage file and folder management into dedicated services

The storage logic for handling files and folders has been reorganized into new dedicated services: StorageFileService, StorageFolderService, and StorageService. This change introduces specific capabilities for managing storage entities, including validating and executing file moves and copies, updating database records (such as file tags and module data) when paths change, and ensuring that file removals correctly unlink related entities. It also adds logic to read the storage directory structure and send it to the frontend, while enforcing path safety to prevent manipulation of files outside the designated upload directory.

src/Services/Module/Storage · high confidence

Refactored travel ideas repository with modern Doctrine interfaces and new query methods

The MyTravelsIdeasRepository has been updated to use modern Doctrine interfaces (ManagerRegistry instead of RegistryInterface) and includes new methods for specific data access patterns: findOneById for retrieving a single entity, getAllNotDeleted for fetching active records, and save for persisting changes. The previous getAllCategories method, which used raw SQL to extract distinct categories, has been removed.

src/Repository/Modules/Travels · high confidence

Removal of Font Awesome 5.8.2 static assets

The static Font Awesome 5.8.2 files, including the license text, the full CSS stylesheet, and the minified CSS file, have been removed from the project. This change eliminates the bundled icon library from the source tree, meaning the application will no longer load these specific local assets for rendering icons.

(repo-wide) · high confidence

Removal of Font Awesome Picker Twig template

The Twig template for the Font Awesome Picker form type has been removed from the codebase. This change eliminates the server-side rendered HTML structure for the icon selection widget, indicating that the frontend implementation for this component has been migrated to a different rendering approach or removed entirely.

templates/core/form-types/fontawesomepicker · high confidence

Removal of FontAwesome and Themify SVG icon fonts

The static SVG font files for FontAwesome and Themify icon sets have been removed from the application. This change eliminates the legacy icon font assets, which will likely require a corresponding update to the UI to use an alternative icon delivery method (such as CSS classes, inline SVGs, or a different font format) to ensure icons continue to display correctly.

src/assets/static · high confidence

Removal of custom DataList form field template

The custom Twig template for the DataList form type has been removed. This template previously rendered a standard HTML input element paired with a datalist tag to provide autocomplete suggestions based on available choices. Its removal means the form field will now rely on the default rendering behavior provided by the underlying framework or parent templates, potentially changing how the input and its options are displayed or styled.

templates/core/form-types/datalist · high confidence

Removal of custom SCSS overrides for Bootstrap Notifications, FontAwesome, and TinyMCE

The custom styling overrides for Bootstrap notifications, FontAwesome icons, and the TinyMCE editor have been removed from the codebase. Specifically, the z-index adjustment for notification containers, the forced FontAwesome font-family application, and various TinyMCE layout fixes (such as status bar background, padding, and image/link wrapping) are no longer applied via these specific SCSS files. Users will now rely on the default styles provided by these libraries or other global stylesheets, which may result in visual changes to notification positioning, icon rendering, and editor layout within modals.

src/scss/libs/customization-for-liblaries · high confidence

Removal of custom error page templates

The custom Twig templates for HTTP error pages (403, 404, 500, and the generic error page) have been deleted from the application. Users will no longer see the previously styled error screens with specific branding and messaging; instead, the application will fall back to the default error handling provided by the underlying framework or server configuration.

templates/bundles/TwigBundle · high confidence

Removal of custom login form template

The custom login form template for the FOSUserBundle has been deleted. Users will no longer see the previously customized login interface (including the specific background image, layout, and styling) and will instead fall back to the default FOSUserBundle login view or another configured template.

templates/bundles/FOSUserBundle/Security · high confidence

Removal of default asset entry points

The default JavaScript and CSS entry files (app.js and app.css) have been removed from the assets directory. This eliminates the pre-configured Webpack Encore setup that previously provided a basic layout style and a console log, requiring users to provide their own asset entry points if they wish to use the asset pipeline.

assets · high confidence

Removal of legacy SCSS entry point and bundled CSS

The \src/scss/index.scss\ entry point and the bundled \src/scss/app.css\ file have been deleted. This removes the static aggregation of external libraries (such as MDB, FontAwesome, and TinyMCE skins) and internal UI modules that were previously imported through this single file, indicating a shift away from the monolithic CSS bundle structure in this directory.

src/scss · high confidence

Removal of legacy Twig templates in My Notes module

The My Notes module has removed its legacy Twig template files (category.html.twig, new-note.html.twig, note-details.html.twig, and settings.html.twig). This change eliminates the server-side rendered views for note categories, creation, details, and settings, indicating a shift away from traditional Twig-based rendering for these specific module interfaces.

templates/modules/my-notes · high confidence

Removal of legacy UI styling modules

The UI styling for several specific modules has been removed from the codebase. The SCSS files for Achievements, Buttons, General layout, My Monthly Payments, My Travels Ideas, and Notes have been deleted. This eliminates custom styles for table actions, toggle switches, quick-access circles, scrollbar customization, sidebar logo positioning, accordion heights, travel idea hover effects, and note list layouts, likely as part of a broader interface scaling or component library migration.

src/scss/ui · high confidence

Removal of legacy charting scripts

The JavaScript initialization files for Chart.js, EasyPieChart, and jQuery Sparkline have been removed from the assets directory. This change eliminates the client-side code responsible for rendering line, bar, area, scatter, pie, and sparkline charts on the dashboard, meaning these visualizations will no longer be rendered by these specific scripts.

src/assets/scripts/charts/chartJS, src/assets/scripts/charts/easyPieChart, src/assets/scripts/charts/sparkline · high confidence

Removal of legacy monthly, product, and settings payment controllers

The \MyPaymentsMonthlyController\, \MyPaymentsProductsController\, and \MyPaymentsSettingsController\ files have been deleted from the application. This removes the legacy PHP controller logic that previously handled the rendering, form submission, and data persistence for monthly payments, product payments, and payment settings (including payment types and currency multipliers). Users relying on these specific controller endpoints for managing these payment aspects will no longer have access to this legacy code path, as the functionality is being migrated to repository-based logic.

src/Controller/Modules/Payments · high confidence

Removed legacy achievements table template

The \table.html.twig\ component for the My Achievements module has been deleted. This removes the previous implementation that rendered achievements in an HTML table with inline styles and inline edit capabilities, indicating a shift in how achievement data is presented or managed within the application.

templates/modules/my-achievements/components · high confidence

Renamed Goals module to Todo and introduced soft-delete support

The entity previously located at src/Entity/Modules/Goals has been renamed to src/Entity/Modules/Todo, with MyGoals becoming MyTodo and MyGoalsSubgoals becoming MyTodoElement. This change includes renaming the database table to my\_todo, updating the namespace, and implementing the SoftDeletableEntityInterface to enable soft-deletion behavior. The data model has also been refactored to support a new relationship with MyIssue and a binding to a generic System Module, while removing the previous subgoal hierarchy.

src/Entity/Modules/Todo · high confidence

Renamed MyCar module to MySchedules

The MyCar repository and its associated schedule types repository have been removed, reflecting the renaming of the MyCar module to MySchedules. This change updates the underlying data access layer to align with the new module naming convention.

src/Repository/Modules/Car · high confidence

Repository layer refactored and extended with new query methods

The repository layer has been updated to use the standard Doctrine ManagerRegistry instead of the Symfony-specific RegistryInterface, affecting MyShoppingPlansRepository and UserRepository. New query capabilities have been added: FilesTagsRepository now supports retrieving tags by file path, updating paths when folders are renamed, and filtering tags by directory; SettingRepository can fetch settings by name; UserRepository includes methods to find users by email or active status; and MyShoppingPlansRepository adds a convenience method to find a plan by ID.

src/Repository · high confidence

Updated Symfony routing configuration and added PHP preloading support

The application now uses Symfony's RoutingConfigurator instead of the deprecated RouteCollectionBuilder, simplifying route imports to YAML files in the config directory. Additionally, a new .preload.php file has been added to support PHP 7.4 preloading by conditionally requiring the preloaded container file if it exists, which may improve performance in production environments.

src · high confidence

User profile settings now use the logged-in user instead of a hardcoded ID

The User profile settings controller has been updated to retrieve the user entity based on the currently authenticated user rather than a static, hardcoded ID (previously \const USER\_ID = 1\). This change ensures that the settings page correctly displays and updates the profile for the specific user who is logged in, preventing crashes or incorrect data access that occurred when multiple users existed or when the hardcoded ID did not match the active session.

src/Controller/User · high confidence

Fixes

Refactored request handling with dedicated kernel listeners and OPTIONS support

The request processing logic in src/Listeners/Request has been reorganized into specific, prioritized kernel listeners to improve modularity and fix existing issues. A new OptionsRequestListener now intercepts browser-generated OPTIONS preflight requests, returning a 200 OK with CORS headers to prevent method-not-allowed errors. Additionally, three new kernel listeners handle distinct concerns: KernelRequestResourceLock (priority 1) enforces module and related-module access restrictions based on locked resources; KernelRequestIpBlock (priority 2) blocks requests from IPs listed in the security configuration; and KernelRequestLogger (priority 3) records detailed request metadata including URL, method, headers, and body content for auditing purposes.

src/Listeners/Request · high confidence

Dependencies

Major platform upgrade: Symfony 4 to 5.4, PHP 7.2 to 8.3, and dependency overhaul

The project has been significantly upgraded, raising the minimum PHP version from 7.2 to 8.3 and migrating the Symfony framework from version 4 to 5.4. This change includes updating core bundles (such as Framework, Security, Mailer, and Form) to their 5.4 equivalents, replacing deprecated packages like SwiftMailer with Symfony Mailer, and removing obsolete dependencies like FOSUserBundle and WebServerBundle. Additionally, the project name has been updated from 'Symfonator' to 'Personal Management System', and new packages for JWT authentication, image resizing, and custom bridges have been added to support the new architecture.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 39.9 → 39.6 (-0.3)
  • Rubric changed (rubric-2026.11.2 → rubric-2026.11.4) — scores are not directly comparable.

Lenses

  • Code Health 56.2 → 55.5 (-0.7)
  • Architecture 81.2 → 85.7 (+4.5)
  • Maturity 52.5 → 48.3 (-4.2)
  • Readiness 20.2 → 21.7 (+1.5)
  • Security 53.0 → 53.0 (0.0)
  • Domain Modelling 84.6 → 84.6 (0.0)

Resolved (34)

  • Abandoned package: sensio/framework-extra-bundle
  • Abandoned package: sensiolabs/security-checker
  • Abandoned package: twig/extensions
  • Critical CVE: [GHSA redacted] (composer.lock)
  • Duplicated block (15 lines × 2) (src/Action/Modules/Contacts/ContactsAction.php)
  • Duplicated block (5 lines × 2) (src/Action/Modules/Job/MyJobHolidaysAction.php)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High CVE: [GHSA redacted] (composer.lock)
  • High secret: WD-SECRET-0005 (package-lock.json)
  • High secret: WD-SECRET-0005 (package.json)
  • Leaked secret: private-key (config/jwt/dev/private.pem)
  • Low CVE: [GHSA redacted] (composer.lock)
  • Low CVE: [GHSA redacted] (composer.lock)
  • Low CVE: [GHSA redacted] (composer.lock)
  • …and 14 more

New (44)

  • Circular dependency (src/Action/File/UploadedFileAction.php)
  • Duplicated block (10 lines × 2) (src/Migrations/Version20191102073301.php)
  • Duplicated block (10 lines × 8) (src/Migrations/Version20190907074501.php)
  • Duplicated block (6 lines × 7) (src/Migrations/Version20190717144649.php)
  • Duplicated block (8 lines × 4) (src/Migrations/Version20190824131917.php)
  • Duplicated block (8 lines × 4) (src/Migrations/Version20190908031047.php)
  • Duplicated block (9 lines × 2) (src/Migrations/Version20191110042650.php)
  • Edited copies of one member (3 members, 12+ corresponding lines) (src/DTO/Settings/Dashboard/SettingsWidgetSettingsDto.php)
  • Edited copies of one member (3 members, 17+ corresponding lines) (src/Repository/Modules/Job/MyJobHolidaysRepository.php)
  • Edited copies of one member (3 members, 19+ corresponding lines) (src/Action/Modules/Health/DoctorAppointmentAction.php)
  • Edited copies of one member (3 members, 20+ corresponding lines) (src/Services/Settings/SettingsSaver.php)
  • Edited copies of one member (3 members, 22+ corresponding lines) (src/Action/Modules/Goals/GoalsPaymentsAction.php)
  • Edited copies of one member (3 members, 6+ corresponding lines) (src/Action/Modules/Goals/GoalsListAction.php)
  • Edited copies of one member (3 members, 9+ corresponding lines) (src/Action/Modules/Health/DoctorAction.php)
  • Edited copies of one member (4 members, 24+ corresponding lines) (src/Action/Modules/Contacts/ContactsAction.php)
  • Edited copy of a member (12 corresponding lines) (src/DTO/Settings/Finances/SettingsCurrencyDto.php)
  • Edited copy of a member (15 corresponding lines) (src/Action/Modules/Issues/MyIssuesAction.php)
  • Edited copy of a member (15 corresponding lines) (src/Action/Modules/System/Settings/Dashboard/WidgetsVisibilityAction.php)
  • Edited copy of a member (15 corresponding lines) (src/DataFixtures/Modules/Issues/MyIssues.php)
  • Edited copy of a member (17 corresponding lines) (src/Services/External/NotifierProxyLoggerService.php)
  • …and 24 more

Changes since last survey

  • 10 commits — 10 feature/other, 0 fixes

By area

  • (root) — 5 commits
  • docker/php-fpm — 1 commit
  • src/Command — 1 commit
  • src/DTO — 1 commit
  • src/Listeners — 1 commit
  • vendor_fixes/full_file_copy — 1 commit

Notable commits

  • change: ⏪️ Re-enable NPL
  • change: ⬆️ Symfony 7.4
  • change: ⬆️ Symfony 7.4.0
  • change: ⬆️ Symfony from 5.x to 6.x, disable NPL temporarily till 7.x
  • change: 🐛 Fresh instance: encryption key gen sets wrong value
  • change: 🐛 S7.4 broke EntityStorageFileHydrationSubscriber
  • change: 📌 Reinstall phpcs
  • change: 📌 Symfony/error-handler 7.4.x
  • change: 🔥 Remove vendor_fixes
  • change: 🚀 Symfony 7.4.x packages to latest versions

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

Volmarg/personal-management-system was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 17 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 1e56150f3356d8d034721189862fd18cc653ff37 — the exact code this score is about.
  • Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.85+preprod-eba6548ac50f.