EdisonJwa
2bbad5feb9
Proof-of-concept proving the Flutter/Rust bridge exit criterion from docs/architecture/proof-of-concept-plan.md §2: "Flutter can call Rust and receive event stream data." The spike exposes one synchronous fallible command (greet) returning a typed GreetResult / GreetError DTO, and one async event stream (counter_stream) emitting typed CounterTick events. The Flutter app demonstrates both flows on a Material 3 surface; the headless test suite in test/poc_verification_test.dart exercises the same API directly through dart:ffi. Verified on 2026-05-13 (Linux desktop, Flutter 3.41.9 / Dart 3.11.5, flutter_rust_bridge 2.12.0, Rust 1.95). All three tests pass: - greet() returns typed result for valid input - greet() surfaces typed error for empty input - counterStream() delivers the expected event sequence Authority: PoC plan §2, DEC-014 (typed Flutter/Rust bridge), SAD-068, SDD-079, SysDes-049. Naming note: the PoC plan lists this as flutter-rust-bridge-hello, but Dart pubspec.yaml package names require underscores; the directory uses underscores accordingly. Not product code; not promoted into chanora_bridge. Layout note: includes the full Flutter platform scaffold (android, ios, macos, windows, web, linux). Only the Linux desktop target has been built and verified.
15 lines
253 B
Plaintext
15 lines
253 B
Plaintext
gradle-wrapper.jar
|
|
/.gradle
|
|
/captures/
|
|
/gradlew
|
|
/gradlew.bat
|
|
/local.properties
|
|
GeneratedPluginRegistrant.java
|
|
.cxx/
|
|
|
|
# Remember to never publicly share your keystore.
|
|
# See https://flutter.dev/to/reference-keystore
|
|
key.properties
|
|
**/*.keystore
|
|
**/*.jks
|