abpframework / abpframework/abp
Consider to implement external localization infrastructure
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
I've created the infrastructure with https://github.com/abpframework/abp/pull/13845
But I haven't implement the IExternalLocalizationStore for open source side yet. Current NullExternalLocalizationStore returns empty results, so it works as before without any problem.
I've implement it for the ABP Commercial language management module. I didn't implement for open source, because there is no module that works with database for localization system and I didn't want to introduce a new module for this purpose. We may use BLOB storing feature, or we can create a generic state storage system (like dapr - see https://github.com/abpframework/abp/issues/16744), then use it. Using distributed cache was not an option because it should be persistent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review pull request 13845 and the IExternalLocalizationStore and NullExternalLocalizationStore entry points first. Compare the existing commercial language management implementation, then evaluate the persistent storage options mentioned, including BLOB storage and issue 16744. Done means an agreed open-source storage approach and a working implementation that preserves current behavior when unused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100