commit | b2689ff9c2b31018ae72408a46e61fed7feca278 | [log] [tgz] |
---|---|---|
author | Todd Volkert <tvolkert@users.noreply.github.com> | Wed Feb 08 08:37:36 2017 -0800 |
committer | GitHub <noreply@github.com> | Wed Feb 08 08:37:36 2017 -0800 |
tree | 9bebbbbb06f4873eeb379c55c6180ef6b2091cd4 | |
parent | 2c08bc1280d363678487bf3dcad931230c801762 [diff] |
Use synchronous file writing in BlobStreamReference (#24) Doing so allows us to avoid dealing in futures all the way back to `encode()`. This becomes important when implementing replay since replay uses `noSuchMethod`, which can't await futures. This also extracts out a few constants in preparation for their use in replay. Part of #11
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();