Skip to content
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

Fix bug in useSharedValueMock #6742

Conversation

sumo-slonik
Copy link
Contributor

@sumo-slonik sumo-slonik commented Nov 21, 2024

Summary

The API for sharedValue has changed from using .value to get() and set() methods. As a result, the mock that previously returned an object with a single value property no longer works in the tests.

Test plan

This is a PR for the mocks, so it's not necessary for it.

use proxy instead of {}
@sumo-slonik sumo-slonik force-pushed the @sumo-slonik/bugfix/fix-use-shared-value-mock branch from c60af3f to 7e3c4ef Compare November 22, 2024 09:45
@sumo-slonik sumo-slonik requested a review from tjzel November 22, 2024 09:55
@tjzel tjzel added this pull request to the merge queue Nov 22, 2024
Merged via the queue into software-mansion:main with commit bff7102 Nov 22, 2024
9 checks passed
tjzel added a commit that referenced this pull request Nov 25, 2024
<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

The API for sharedValue has changed from using .value to get() and set()
methods. As a result, the mock that previously returned an object with a
single value property no longer works in the tests.

## Test plan

This is a PR for the mocks, so it's not necessary for it.

---------

Co-authored-by: Tomasz Żelawski <[email protected]>
@tjzel tjzel mentioned this pull request Nov 25, 2024
tjzel added a commit that referenced this pull request Nov 26, 2024
<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

The API for sharedValue has changed from using .value to get() and set()
methods. As a result, the mock that previously returned an object with a
single value property no longer works in the tests.

## Test plan

This is a PR for the mocks, so it's not necessary for it.

---------

Co-authored-by: Tomasz Żelawski <[email protected]>
tjzel added a commit that referenced this pull request Dec 13, 2024
<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

The API for sharedValue has changed from using .value to get() and set()
methods. As a result, the mock that previously returned an object with a
single value property no longer works in the tests.

## Test plan

This is a PR for the mocks, so it's not necessary for it.

---------

Co-authored-by: Tomasz Żelawski <[email protected]>
tjzel added a commit that referenced this pull request Dec 13, 2024
<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

The API for sharedValue has changed from using .value to get() and set()
methods. As a result, the mock that previously returned an object with a
single value property no longer works in the tests.

## Test plan

This is a PR for the mocks, so it's not necessary for it.

---------

Co-authored-by: Tomasz Żelawski <[email protected]>
tjzel added a commit that referenced this pull request Dec 13, 2024
<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

The API for sharedValue has changed from using .value to get() and set()
methods. As a result, the mock that previously returned an object with a
single value property no longer works in the tests.

## Test plan

This is a PR for the mocks, so it's not necessary for it.

---------

Co-authored-by: Tomasz Żelawski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants