---
title: Data
description: An in-memory store, a row type, and a mapper. This is where the API client would sit.
tags: [clean-architecture, flutter]
---

`lib/features/notes/data/`. The repository implementation is inside the feature. The composition root is the only file outside the feature that imports it. `NoteStore` is an in-memory list of rows. The repository does not call HTTP.

```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](../../layers/infrastructure.md): run the invariant on load, or fail the load.

The files are [`lib/features/notes/data/note_row.dart`](https://github.com/newtalaria/clean-architecture/blob/main/examples/flutter/feature_first/lib/features/notes/data/note_row.dart) and [`lib/features/notes/data/note_repository_impl.dart`](https://github.com/newtalaria/clean-architecture/blob/main/examples/flutter/feature_first/lib/features/notes/data/note_repository_impl.dart). `flutter test` starts no server because the list is the store.

Next: [Presentation](presentation.md).