commit | 53c69dfa0d2f31a8662309906b411579c10af2ca | [log] [tgz] |
---|---|---|
author | Todd Volkert <tvolkert@users.noreply.github.com> | Mon Feb 06 17:27:49 2017 -0800 |
committer | GitHub <noreply@github.com> | Mon Feb 06 17:27:49 2017 -0800 |
tree | 7cc09a81faf3ca14bceb1a4eae4b849f04e65dd1 | |
parent | 722d092cadc35b8a3647667778daa2739da71161 [diff] |
Clean up a few things in the record_replay library: (#22) - use closures rather than subclasses to reduce some code in recording_file.dart - `basename` and `dirname` were missing from `RecordingFileSystemEntity` - `RecordingFileSystemEntity` didn't need to use two parameterized types. That was an artifact of it having forked from `ForwardingFileSystemEntity` - Change the name pattern of the blob files to use the basename of the `RecordingFile` rather than the name of method being recorded
A generic file system abstraction for Dart.
Like dart:io
, package:file
supplies a rich Dart-idiomatic API for accessing a file system.
Unlike dart:io
, package:file
:
Implement your own custom file system:
import 'package:file/file.dart'; class FooBarFileSystem implements FileSystem { ... }
Use the in-memory file system:
import 'package:file/memory.dart'; var fs = new MemoryFileSystem();
Use the local file system (requires dart:io access):
import 'package:file/local.dart'; var fs = const LocalFileSystem();