sourcefuse / sourcefuse/loopback4-microservice-catalog
@sourceloop/notification-service - dynamic data in db
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 297
- Forks
- 78
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
Right now we save the entire email body in the db
instead we should give a configurable feature that only saves the dynamic fields in the db and not the entire body
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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
The issue names @sourceloop/notification-service but provides no files, tests, or entry points to inspect. First clarify the configuration, dynamic-field format, and expected database behavior; the work is complete when the service can be configured to save only dynamic fields instead of the full email body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100