-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
chore(tests): add simple tests for ref rerender and subscription #88
Merged
dai-shi
merged 2 commits into
pmndrs:master
from
YPAzevedo:ypazevedo/add-simple-ref-tests
Feb 20, 2021
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
import { proxy, subscribe } from '../src/index' | ||
import { proxy, ref, subscribe } from '../src/index' | ||
|
||
describe('subscribe', () => { | ||
it('should call subscription', async () => { | ||
|
@@ -83,4 +83,16 @@ describe('subscribe', () => { | |
await Promise.resolve() | ||
expect(handler).toBeCalledTimes(1) | ||
}) | ||
|
||
it('should not call subscription for objects wrapped in ref', async () => { | ||
const obj = proxy({ nested: ref({ count: 0 }) }) | ||
const handler = jest.fn() | ||
|
||
subscribe(obj, handler) | ||
|
||
obj.nested.count += 1 | ||
|
||
await Promise.resolve() | ||
expect(handler).toBeCalledTimes(0) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is probably ok. |
||
}) | ||
}) |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this check is weak. It doesn't guarantee that the count keeps
0
, does it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you double check if this fails if you remove
ref
? I might be wrong though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it does still pass without ref 🤔 what would be your recommendation here to make the test stronger?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added the wait for the Promise.resolve to make the assertion of findByText wait for the changes to be flushed. now it fails with no ref 😀
no ref - count: 0 - count: 0 -> FAIL
no ref - count: 0 - count: 1 -> PASS
ref - count: 0 - count: 0 -> PASS
ref - count: 0 - count: 1 -> FAIL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I wasn't so sure about the best way.
Promise.resolve() is a nice hack, even though it depends on some implementation details. We are doing it in other tests, anyway.
Good to go. And hope someone has a better idea in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, thanks! i'll see if theres a better solution and update this and the other tests! 👍