fix: app rendered event latency calculation #273
Merged
Conversation
This file contains 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
vsrivatsa-edinburgh
requested review from
prafulkoppalkar and
ArushKapoorJuspay
as code owners
vsrivatsa-edinburgh
force-pushed
the
fix/app_rendered_latency_calculation
branch
from
a47ec5e
to
3b8bf91
Compare
PritishBudhiraja
approved these changes
Apr 4, 2024
prafulkoppalkar
approved these changes
Apr 4, 2024
akash-c-k
pushed a commit
that referenced
this pull request
Apr 4, 2024
rising-dragon401
added a commit
to rising-dragon401/hyperswitch-web
that referenced
this pull request
Jul 2, 2024
# [0.37.0](juspay/hyperswitch-web@v0.36.2...v0.37.0) (2024-04-04) ### Bug Fixes * app rendered event latency calculation ([#273](juspay/hyperswitch-web#273)) ([e3509f0](juspay/hyperswitch-web@e3509f0)) ### Features * logging payment data filled ([#269](juspay/hyperswitch-web#269)) ([e9d76ae](juspay/hyperswitch-web@e9d76ae))
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.
Type of Change
Description
Fix for APP_RENDERED event latency calculation
Motivation and Context
How did you test it?
By observing latency value in the logs containing the APP_RENDERED event_name
Checklist
npm run re:build