Phase A: generierter Dart-Client + DI-Foundation für Rust-Backend
OpenAPI-Generator-Setup: - tool/generate_api_client.sh: Direkter Aufruf der openapi-generator-cli.jar (Java-CLI statt Dart-build_runner-Integration — vermeidet die analyzer-/source_gen-Version-Hölle mit json_serializable) - tool/fetch_openapi_generator.sh: lädt die JAR (29 MB) nach (gitignored) - openapi/holzleitner.json: Snapshot der Backend-Spec für reproduzierbare Generation - packages/holzleitner_api/: generiertes Dart-Sub-Package (built_value + dio), per path-dep im Haupt-pubspec eingehängt Netzwerk-Layer (lib/data/network/): - BackendConfig: API- und Keycloak-Endpoints für Local-Dev (localhost wegen Keycloak-iss-Claim). - AuthTokenProvider-Schnittstelle. - DevPasswordGrantTokenProvider: Phase-A-Provider via Keycloak password-grant, Token-Caching mit Expiry-Check (Phase B ersetzt das durch flutter_appauth PKCE). - HolzleitnerAuthInterceptor: dynamischer Bearer-Inject pro Request. - HolzleitnerApiFactory: baut die generierte HolzleitnerApi-Klasse mit unserem Interceptor statt der vier Default-Auth-Interceptors. - network_locator.registerNetworking(): get_it-Setup, in main() vor runApp() aufgerufen. Clean-Arch-Scaffolding (lib/data/, lib/domain/): - Verzeichnisstruktur für Phase C+D angelegt (mapper/, repository/, entity/, repository/) — befüllt sich in den Folge-Phasen. Smoke-Test: - tool/smoke_test_api.dart ruft /health (ungeschützt) und /me/cars (mit Bearer) via generiertem Client — grün gegen lokales Backend.
This commit is contained in:
42
packages/holzleitner_api/lib/src/model/scan_status.dart
Normal file
42
packages/holzleitner_api/lib/src/model/scan_status.dart
Normal file
@ -0,0 +1,42 @@
|
||||
//
|
||||
// AUTO-GENERATED FILE, DO NOT MODIFY!
|
||||
//
|
||||
|
||||
// ignore_for_file: unused_element
|
||||
import 'package:built_collection/built_collection.dart';
|
||||
import 'package:built_value/built_value.dart';
|
||||
import 'package:built_value/serializer.dart';
|
||||
|
||||
part 'scan_status.g.dart';
|
||||
|
||||
class ScanStatus extends EnumClass {
|
||||
|
||||
/// Status einer einzelnen Scan-Position innerhalb eines Items.
|
||||
@BuiltValueEnumConst(wireName: r'in_progress')
|
||||
static const ScanStatus inProgress = _$inProgress;
|
||||
/// Status einer einzelnen Scan-Position innerhalb eines Items.
|
||||
@BuiltValueEnumConst(wireName: r'done')
|
||||
static const ScanStatus done = _$done;
|
||||
/// Status einer einzelnen Scan-Position innerhalb eines Items.
|
||||
@BuiltValueEnumConst(wireName: r'held')
|
||||
static const ScanStatus held = _$held;
|
||||
/// Status einer einzelnen Scan-Position innerhalb eines Items.
|
||||
@BuiltValueEnumConst(wireName: r'removed')
|
||||
static const ScanStatus removed = _$removed;
|
||||
|
||||
static Serializer<ScanStatus> get serializer => _$scanStatusSerializer;
|
||||
|
||||
const ScanStatus._(String name): super(name);
|
||||
|
||||
static BuiltSet<ScanStatus> get values => _$values;
|
||||
static ScanStatus valueOf(String name) => _$valueOf(name);
|
||||
}
|
||||
|
||||
/// Optionally, enum_class can generate a mixin to go with your enum for use
|
||||
/// with Angular. It exposes your enum constants as getters. So, if you mix it
|
||||
/// in to your Dart component class, the values become available to the
|
||||
/// corresponding Angular template.
|
||||
///
|
||||
/// Trigger mixin generation by writing a line like this one next to your enum.
|
||||
abstract class ScanStatusMixin = Object with _$ScanStatusMixin;
|
||||
|
||||
Reference in New Issue
Block a user