Rody Davis
Rody Davis
Oh interesting... Looking into this. I am not sure if there is a way to check if the ValueListenable/ValueNotifier is actually disposed: https://api.flutter.dev/flutter/foundation/ChangeNotifier/dispose.html There is a private variable to check...
That is correct, this is to match Angular behavior! You can add them manually in the dependencies array
Oh interesting... there must be a null check. I think I know what would cause it too
Thanks for the added context! This is super tricky and I am tempted to consider this undefined behavior and to suggest the set/force option for nullable types.
Thank you for this! I fixed it with a recent commit and will update the package soon
The reason I did this was because it was not showing up when I extended the signal vs invoked the constructor directly. Maybe my duplication is no longer needed!
I am working on updating this with a new version I created based on the open xml spec. You could query for elements and modify directly. The part that is...
I can't update archive yet because there is a breaking change on the archive file. Happy to accept a PR for the fix though