History

Bernhard Müller 975f76dbd3 feat(community): add metering data upload and query with XLSX support Implement complete metering data management for energy communities: - MeteringData entity with unique constraint (metering_point_id, interval_start, data_type) - Bulk upload via JSON or XLSX (multipart) with validation - XLSX parser using Apache POI with comma-decimal support - Ownership check on GET endpoints (userId must match metering point owner) - Deduplication: existing records overwritten on re-upload - DataSource tracking (EMAIL_XLSX, API, MANUAL) - Query endpoints: by metering point, by type, by upload batch Additional fixes: - MapStruct annotation processor: add to execution-level annotationProcessorPaths (Spring Boot parent POM was overriding plugin-level config) - EnergyCommunityMapper + MeteringDataMapper: componentModel=spring - UserMapper: ignore passwordResetToken/Expiry (unmapped target policy ERROR) - TariffService: add TariffInviteRepository dependency + invitation check - TariffServiceTest: add missing @Mock for TariffInviteRepository - SecurityConfig: permit /actuator/health and /actuator/info - pom.xml: add poi-ooxml, postgresql, spring-boot-starter-actuator - .gitignore: add *.log, survey/, backend.log Tests: 137/137 passing		2026-07-22 12:42:27 +02:00
..
public	first working frontend/backend	2026-06-01 16:59:49 +02:00
src	feat(dashboard): add pending memberships card to admin overview	2026-07-22 10:59:01 +02:00
.editorconfig	first working frontend/backend	2026-06-01 16:59:49 +02:00
.gitignore	first working frontend/backend	2026-06-01 16:59:49 +02:00
.postcssrc.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
.prettierrc	first working frontend/backend	2026-06-01 16:59:49 +02:00
angular.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
openapi.yaml	feat(community): add metering data upload and query with XLSX support	2026-07-22 12:42:27 +02:00
openapitools.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
package-lock.json	added admin approval list	2026-06-17 11:08:44 +02:00
package.json	added admin approval list	2026-06-17 11:08:44 +02:00
pom.xml	first working frontend/backend	2026-06-01 16:59:49 +02:00
proxy.conf.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
README.md	first working frontend/backend	2026-06-01 16:59:49 +02:00
tsconfig.app.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
tsconfig.json	first working frontend/backend	2026-06-01 16:59:49 +02:00
tsconfig.spec.json	first working frontend/backend	2026-06-01 16:59:49 +02:00

README.md

EegFrontend

This project was generated using Angular CLI version 21.2.12.

Development server

To start a local development server, run:

ng serve

Once the server is running, open your browser and navigate to http://localhost:4200/. The application will automatically reload whenever you modify any of the source files.

Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

ng generate component component-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

Building

To build the project run:

ng build

This will compile your project and store the build artifacts in the dist/ directory. By default, the production build optimizes your application for performance and speed.

Running unit tests

To execute unit tests with the Vitest test runner, use the following command:

ng test

Running end-to-end tests

For end-to-end (e2e) testing, run:

ng e2e

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.