Data

An in-memory store, a row type, and a mapper. This is where the API client would sit.

clean-architectureflutter

lib/data/notes/. The row and the repository implementation sit in the data layer, named for the feature. NoteStore is an in-memory list of rows. The repository does not call HTTP. The wrapped client in Composition root is the hook a real API call would use.

dart

factory NoteRow.fromNote(Note note) {
  return NoteRow(
    id: note.id,
    title: note.title,
    body: note.body,
    createdAtMicros: note.createdAt.microsecondsSinceEpoch,
  );
}

save appends a row and returns nothing. findAll maps each row with toNote, which uses the Note constructor. Rows here were written after Note.create, so the list keeps a title the domain already accepted. A store that can hold a row create would refuse should follow Infrastructure: run the invariant on load, or fail the load.

The files are lib/data/notes/note_row.dart and lib/data/notes/note_repository_impl.dart. flutter test starts no server because the list is the store.

Next: Presentation.