-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename callback
parameter in Watcher.attach
and make it named onChange
#37
Comments
PackRuble
added a commit
that referenced
this issue
Feb 10, 2025
- upd: minimum supported SDK version to Flutter 3.24.0/Dart 3.5.0 - 🛡️fix: [Implement security advisories CWE-502](#29) - new: now you can directly create an instance of the `Cardoteka` ([#15](#15)) - new: `CardotekaAsync` for asynchronous data retrieval (works without cache) ([#24](#24)) - 🧨upd: all declarations of own classes from `Cardoteka` and `CardotekaAsync` must now necessarily be declared as `final` or `base` or `sealed` - 🧨upd: `AccessToSP` has been deleted. Use `import package:cardoteka/access_to_sp.dart`. - 🧨upd: changes in `Watcher.attach`: `onRemove` parameter is now required and callback is now a named `onChange` parameter ([#14](#14) и [#37](#37)) - add: `Detachability` and `DetacherChangeNotifier`for easy dispose of linked resources in classes with business logic ([#10](#10) и [#9](#9)) - add: `CRUD.readAsync` method for use with `CardotekaAsync` - add: `notifyAll` method for `Watcher` [17](#17) - upd: `Converters.colorAsInt` is temporarily deprecated. See more details in [#31](#31) - add: `CardotekaCore.migrate` method for data migration ([#33](#33)) - upd: all examples in `example` folder have been updated - upd: some internal methods have been hidden from the IDE prompts to make package easier to use - doc: "Notifier (riverpod)", "Analogy in `SharedPreferencesWithCache` and `SharedPreferencesAsync`", "Migration", "Sync or Async storage", "Detachability" sections were added to readme You can see all closed issues in [Milestone v2.0.0](https://github.com/PackRuble/cardoteka/milestone/2?closed=1). Also, read `readme.md` section on data migration [Cardoteka from v1 to v2](https://github.com/PackRuble/cardoteka?tab=readme-ov-file#cardoteka-from-v1-to-v2).
PackRuble
added a commit
that referenced
this issue
Feb 10, 2025
- upd: minimum supported SDK version to Flutter 3.24.0/Dart 3.5.0 - 🛡️fix: [Implement security advisories CWE-502](#29) - new: now you can directly create an instance of the `Cardoteka` ([#15](#15)) - new: `CardotekaAsync` for asynchronous data retrieval (works without cache) ([#24](#24)) - 🧨upd: all declarations of own classes from `Cardoteka` and `CardotekaAsync` must now necessarily be declared as `final` or `base` or `sealed` - 🧨upd: `AccessToSP` has been deleted. Use `import package:cardoteka/access_to_sp.dart`. - 🧨upd: changes in `Watcher.attach`: `onRemove` parameter is now required and callback is now a named `onChange` parameter ([#14](#14) и [#37](#37)) - add: `Detachability` and `DetacherChangeNotifier`for easy dispose of linked resources in classes with business logic ([#10](#10) и [#9](#9)) - add: `CRUD.readAsync` method for use with `CardotekaAsync` - add: `notifyAll` method for `Watcher` [#17](#17) - upd: `Converters.colorAsInt` is temporarily deprecated. See more details in [#31](#31) - add: `CardotekaCore.migrate` method for data migration ([#33](#33)) - upd: all examples in `example` folder have been updated - upd: some internal methods have been hidden from the IDE prompts to make package easier to use - doc: "Notifier (riverpod)", "Analogy in `SharedPreferencesWithCache` and `SharedPreferencesAsync`", "Migration", "Sync or Async storage", "Detachability" sections were added to readme You can see all closed issues in [Milestone v2.0.0](https://github.com/PackRuble/cardoteka/milestone/2?closed=1). Also, read `readme.md` section on data migration [Cardoteka from v1 to v2](https://github.com/PackRuble/cardoteka?tab=readme-ov-file#cardoteka-from-v1-to-v2).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given that I've decided to change #14, it would be nice if our api was more "bare-bones"
The text was updated successfully, but these errors were encountered: