-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Check observer #111
Check observer #111
Conversation
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
==========================================
+ Coverage 95.5% 95.51% +<.01%
==========================================
Files 40 40
Lines 1445 1448 +3
==========================================
+ Hits 1380 1383 +3
Misses 65 65
Continue to review full report at Codecov.
|
can we make this optional? Thanks in advance |
I think a middle ground would be to not throw an AssertionError and instead only print a warning to the console. Can you send a PR, @kholdunn ? If you are not sure, I can help you out. |
@pavanpodila
I tried that, it is showing this error
|
looks like you have other layout related error here. Also, you don't need an Observer if you are not watching any observable. |
@pavanpodila That's correct, but in my case, I'm using my own widget class which extends a native widget. In the constructor, I'm receiving the properties and overriding them, by that, I might override all default properties, then I won't be able to have an observable.
|
@kholdunn Interesting use case. Can you file an issue for this. I'll work on it next week. |
This will check the builder function and assert if no observables are detected. I ran into this issue a few days back and took quite some time to figure out that there were no observables being tracked inside! I think this is a good sanity check to have.