Mike Kell
9eafc68fec
Validate Docs / validate-docs (push) Successful in 1m13s
Details
Extract AppConfig/AppEnvironment, AppServices, Bootstrap, and AppScope into core package as KcAppConfig, KcAppServices, KcBootstrap, and KcAppScope generic abstractions. New core composition types: - KcAppConfig: runtime config from --dart-define (KC_ENV, WC credentials) - KcAppEnvironment: enum for fake/wordpress environments - KcAppServices: abstract base for app service containers - KcServiceFactory<T>: generic factory for fake/wordpress service creation - KcBootstrap: shared bootstrap with env switch and WP credential fallback - KcAppScope<T>: InheritedWidget exposing typed services + config to tree kell_web backward compatibility: - AppConfig/AppEnvironment are now typedefs to Kc-prefixed types - AppServices extends KcAppServices with concrete repositories - AppScope extends KcAppScope<AppServices> with direct InheritedWidget lookup - Bootstrap delegates to KcBootstrap.run with app-specific factory Tests: 20 new core tests, all 379 tests passing (core 20, design_system 41, feature_wordpress 294, kell_web 24). dart analyze clean. |
||
|---|---|---|
| .. | ||
| lib | ||
| test | ||
| .gitignore | ||
| .metadata | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| analysis_options.yaml | ||
| pubspec.yaml | ||
README.md
TODO: Put a short description of the package here that helps potential users know whether this package might be useful for them.
Features
TODO: List what your package can do. Maybe include images, gifs, or videos.
Getting started
TODO: List prerequisites and provide or point to information on how to start using the package.
Usage
TODO: Include short and useful examples for package users. Add longer examples
to /example folder.
const like = 'sample';
Additional information
TODO: Tell users more about the package: where to find more information, how to contribute to the package, how to file issues, what response they can expect from the package authors, and more.