You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this library to track INP in a large single page app. Sessions with the app can be long -- sometimes hours. We are interested in collecting INP over a smaller time range, rather than for an entire session. The docs indicate that it's important to track changes to INP over time, but INP as reported by this library is only ever increasing. So, it doesn't reflect the experience that a user is having for a given, say, 10 minute span of a session.
I was wondering if there has been any thought about exposing a function that resets the internal state for a given metric. I can fork the library and implement what I need for our use case (e.g., it seems like this might be close to the behavior we need), but I'm wondering if others have run into this, or if there's something I'm missing about my understanding of the library and its best practices.
The text was updated successfully, but these errors were encountered:
We are using this library to track INP in a large single page app. Sessions with the app can be long -- sometimes hours. We are interested in collecting INP over a smaller time range, rather than for an entire session. The docs indicate that it's important to track changes to INP over time, but INP as reported by this library is only ever increasing. So, it doesn't reflect the experience that a user is having for a given, say, 10 minute span of a session.
I was wondering if there has been any thought about exposing a function that resets the internal state for a given metric. I can fork the library and implement what I need for our use case (e.g., it seems like this might be close to the behavior we need), but I'm wondering if others have run into this, or if there's something I'm missing about my understanding of the library and its best practices.
The text was updated successfully, but these errors were encountered: