This is a demo for a solution to a niche business problem.
Say, you have a large amount of copies for use in your product UI.
These would be put somewhere in i18n files and updated as part of CI/CD process but domain experts want to be able to edit them and quickly apply the updates to UI. This requirement and the amount of edit requests make this too tedious to support using standard i18n mechanisms.
The solution here demonstrates how to consume the copies stored on backend in a way that:
- doesn't require constant backend adjustments
- allows minimal adjustments to front-end setup when a new value is required or existing value changes its structure.
- Run backend API located in
KnowledgeBaseService
usinghttp
orhttps
launch profile. The configured setup expects it to run on localhost:8100. - Run
npm install
and thennpm run start
for thedemo-frontend
project. You should be able to access the demo at http://localhost:4200 and see the examples of resolved data queries.
- Check entry-types.ts and entry-spec.ts to understand how query setup works.
- Check Noce.ExpertKnowledge.WebApi.http for a sample request.
- Dummy knowledge entry spec resolver returns a value based on the requested key for simplicity.