abpframework / abpframework/abp
split /api/abp/application-configuration
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
For a large application putting localization in the configuration file is a waste of bandwidth.
Configuration might change an app path or load method, etc, no need to heavy weight it.
Abp is modular, so why does it load all strings at once, if you have 100 modules, that is a lot of string. Proper way is to load localization at the time as module is activated.
Nothing is modular if you load strings on app startup.
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
Start by tracing the /api/abp/application-configuration endpoint and how it loads localization for modules. Determine how configuration can be separated from localization and loaded when a module is activated. Done means the endpoint no longer loads all module strings at application startup while still providing localization when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100