Add optional minimumVarianceUnit to GetTimeAgo.parse for custom stopping points #37
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.
Pull Request Checklist
What does this PR do?
This PR introduces an optional minimumVarianceUnit parameter to the GetTimeAgo.parse method, allowing users to specify a unit (seconds, minutes, hours, days) to act as a threshold. When the elapsed time is less than this threshold, the method returns “Less than [Unit]”. If the elapsed time is less than 15 seconds, it always returns “Just now”. If the parameter is not provided, the method retains its original behavior.
Checklist
Code Changes
Documentation
pubspec.yaml
fileTesting
General Tests
Localization
Custom Thresholds
Error Handling
Responsiveness
Performance
How did you verify your code works?
I ran manual tests to verify time formatting for different locales and thresholds