improvement - ignore noise triggeres on the minimumViewTime config - #56191
ARIPRASATH4664 wants to merge 1 commit into
Conversation
|
Hi @ARIPRASATH4664! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
This PR is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label. |
I have been working on a chat application and dependent on the inView callbacks every time to have certain followup actions, Due to this piled up setTimeout execution there is too much of noise which is already outdated as the timeout never ensure it is resolved immediately after the config
Summary:
Clear the previous timers and reply back with the latest inView, the noise and irrelevant reports on the previous state is cleared out
Changelog:
Pick one each for the category and type tags:
[ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message
GENERAL - CHANGED
For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests
-->
Test Plan: