Correctly export fireEvent from renderer.ts #143
Merged
Conversation
This file contains hidden or 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
marlonicus
added a commit
that referenced
this pull request
Apr 8, 2025
* Update renderer.ts to export fireEvent correctly * Approach to export testing library while overriding fireEvent * Export with disabled rules.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The renderer sets up the
fireEventfunction to call the correctactimplementation. However this wrappedfireEventis not actually exported from the package, and instead the "empty"fireEventfromtesting-libraryis exported instead.This PR exports the correctly wrapped
fireEventfunction for use.