Calling callback functions directly (eg. for tests) #1839
Merged
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.
As per #1195, sometimes there's a need to unit-test some of the callback functions. What we're doing in the team right now is adding a wrapper so that the callback calls a wrapper and we're able to call the function outside of the dash framework.
Initially I thought that what has been suggested in the issue description would be more appropriate (so, having
.inner
attribute on the returned value), but eventually the other suggested solution is more "intuitive" (in the former case, we'd have to update the documentation as well :( )The solution is not ideal, obviously, cause if somebody uses the callback context within the callbacks which he/she intends to call in isolation, it's gonna crash (unless it's somehow mocked in the calling context)
Contributor Checklist
optionals
CHANGELOG.md