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
The lack of that configurable makes it impossible to work with DateOnly parameters when the native Date object is being used and the current user is on negative timezone offset.
When this parameter is set to true, DateOnly conversion should use the method parseDateOnly that converts the Date to the local time zone.
The text was updated successfully, but these errors were encountered:
gabrielheming
changed the title
Missing ConvertDateToLocalTimezone parameter from OpenApiToTypeScriptClientCommand
Missing ConvertDateToLocalTimezone parameter from TypeScriptClientGeneratorSettings
Jan 9, 2025
gabrielheming
changed the title
Missing ConvertDateToLocalTimezone parameter from TypeScriptClientGeneratorSettings
Missing ConvertDateToLocalTimezone parameter on TypeScriptClientGeneratorSettings and OpenApiToTypeScriptClientCommandJan 9, 2025
Describe the bug
Following this PR, the parameter
ConvertDateToLocalTimezone
was added to configure whether the DateOnly conversion should be to local or no. However, the parameter does not exists on the settings TypeScriptClientGeneratorSettings and also does not exists on OpenApiToTypeScriptClientCommand.The lack of that configurable makes it impossible to work with DateOnly parameters when the native Date object is being used and the current user is on negative timezone offset.
Version used
Tested with version 14.2.0 from npm
Expected behavior
When this parameter is set to true, DateOnly conversion should use the method parseDateOnly that converts the Date to the local time zone.
The text was updated successfully, but these errors were encountered: