Skip to content

Commit ece9fb7

Browse files
authored
Merge pull request #2 from roughike/release/v1.0.1
v1.0.1
2 parents 610d919 + e02e046 commit ece9fb7

File tree

4 files changed

+5
-6
lines changed

4 files changed

+5
-6
lines changed

CHANGELOG.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,5 @@
1+
## 1.0.1
2+
* [#1](https://github.com/roughike/streaming_shared_preferences/pull/1): Fix a bug where reusing a `Preference` between multiple listeners only propagated the change to the first one.
3+
14
## 1.0.0
25
* Initial stable release.

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ If you're already using `shared_preferences`, **you should replace the dependenc
1616

1717
```yaml
1818
dependencies:
19-
streaming_shared_preferences: ^1.0.0
19+
streaming_shared_preferences: ^1.0.1
2020
```
2121
2222
To get a hold of `StreamingSharedPreferences`, _await_ on `instance`:

pubspec.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
name: streaming_shared_preferences
22
description: A stream based wrapper over shared_preferences, allowing reactive key-value storage.
3-
version: 1.0.0
3+
version: 1.0.1
44
author: Iiro Krankka <[email protected]>
55
homepage: https://github.com/roughike/streaming_shared_preferences
66

test/preference/preference_test.dart

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,16 +118,12 @@ void main() {
118118
expect(value2, 'default value');
119119
expect(value3, 'default value');
120120

121-
// The value passed to setValue does not matter in tests - it just merely
122-
// triggers the preference that something just changed.
123121
await _updateValue('first change');
124122

125123
expect(value1, 'first change');
126124
expect(value2, 'first change');
127125
expect(value3, 'first change');
128126

129-
// The value passed to setValue does not matter in tests - it just merely
130-
// triggers the preference that something just changed.
131127
await _updateValue('second change');
132128

133129
expect(value1, 'second change');

0 commit comments

Comments
 (0)