Preserve offset values in progress tracking events parsing #486
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
clarissedmn
force-pushed
the
preserve-offset-values
branch
3 times, most recently
from
147c837 to
955e231
Compare
clarissedmn
force-pushed
the
preserve-offset-values
branch
3 times, most recently
from
aa50487 to
276c1b4
Compare
clarissedmn
force-pushed
the
preserve-offset-values
branch
from
276c1b4 to
e5e1ce3
Compare
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.
Description
The precision of Progress tracking events in VAST XML has been improved to preserve the exact offset value in its original format, whether time-based (e.g., 00:00:15.333) or percentage-based (e.g., 60%). The parsing logic has been refined to ensure these values are accurately retained, providing greater reliability and flexibility.
Below is an example showing the improvement:
Issue
#485
Type