fix: Manual entries now correctly parse local time #73
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.
Replaced usage of time.Local with settings.GetDisplayTimezone() in date parsing and display functions. Also exported GetDisplayTimezone for use outside the settings package, ensuring consistent timezone handling based on user configuration.
Pull Request Checklist
mainbranch of tmpo.Description
This pull request updates how the application handles time zones by ensuring that all date and time parsing and formatting consistently use the user's configured display timezone instead of the local system timezone. The changes primarily involve switching from the local timezone to a configurable display timezone throughout the codebase.
Timezone handling improvements:
parseDateTimefunction incmd/entries/manual.goto usesettings.GetDisplayTimezone()instead oftime.Localfor all date and time parsing, ensuring user-configured timezone is respected.getDisplayTimezonefunction toGetDisplayTimezoneininternal/settings/global_config.goto make it accessible outside the package.toDisplayTimefunction to use the newly exportedGetDisplayTimezonefor converting UTC time to the user's display timezone.