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

Makes sure to return promise from setObject logic. … #2967

Merged
merged 7 commits into from
Nov 27, 2024

Conversation

Apollon77
Copy link
Collaborator

Affects setObject and extendObject at least

Implementation details
Return the promise from _setObjectWithDefaultValue to the calling method else this gets lost when no callback was provided

Tests

  • I have added tests to avoid a recursion of this bug
  • It is not possible to test for this bug

If no tests added, please specify why it was not possible
change is too obbvious :-)

@foxriver76
Copy link
Collaborator

foxriver76 commented Nov 17, 2024

After merging we should depreacte setObjectAsync (else we loose track of whats already working) in a separate PR and maybe also add a test, that setObject works correctly promise-based. Or I can also add it as part of this PR if you like @Apollon77

foxriver76 and others added 2 commits November 27, 2024 19:15
* deprecate setObjectAsync/setForeignObjectAsync

* added tests
and corrected types

* fix the test
@foxriver76 foxriver76 merged commit 2c4baa4 into master Nov 27, 2024
15 checks passed
@foxriver76 foxriver76 deleted the fix-setopbject-return branch November 27, 2024 19:08
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.

3 participants