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
In addressing a problem, I discovered that:
new BikramSambat()
BikramSambat.fromAD(new Date())
were producing inconsistent results.
The issue arose because, when creating a new instance of BikramSambat, the current date was converted to an ISO string and then sliced to reset the UTC hours to 00:00:00. However, when using the static method directly (BikramSambat.fromAD(new Date())), the UTC handling led to slight discrepancies, causing the date calculation to be offset by one day.
Issue Reference
Inconsistent output #48
Proposed Changes
To ensure consistent results between both approaches, I've applied uniform UTC handling for date calculations, maintaining the same logic for resetting the date to 00:00:00 in UTC.
Screenshots / GIFs / Videos
Checklist