This repository has been archived by the owner on Jan 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
37 additions
and
12 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Below are some details relating to localization support | ||
|
||
The EF model builders for both Mssql and Postgres generate tables with | ||
* datetime fields which store timezone | ||
* string fields which support unicode | ||
|
||
When coding you should always save dates as local UTC time. Datetime values are *implicitly converted* for any requests handled by Asp.NET Core controllers. This is done by registering a | ||
|
||
* custom modelbinder (for handling inbound datetime values) | ||
* custom json formatter (for handling both inbound and outbound datetime values) | ||
|
||
Each of the above customizations to the pipeline uses an injected instance of IHttpServiceContextResolver to return an instance of IDomainContext. The IDomainContext exposes the current | ||
|
||
* culture | ||
* timezone | ||
* user details | ||
|
||
The ILocalizationService can be used to get a full list of all supported cultures, timezones, and create a dictionary of culture-specific resource strings. | ||
|
||
The default implementation of the localization service is thread-safe. | ||
|