fix(general-petitions): updating email in endorsement system service

[albinagu]

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Formatting passes locally with my changes
• I have rebased against main before asking for a review

Summary by CodeRabbit

• Chores
  • Updated the recipient email address for new endorsement list notifications. The log message now reflects the new recipient address.

[coderabbitai]

Walkthrough

The recipient email address and name used in the emailCreated method of the EndorsementListService class were updated from "[email protected]" to "[email protected]". The corresponding log message was also modified to reflect this change. No other logic or structural changes were made.

Changes

File(s)	Change Summary
apps/services/endorsements/api/src/app/modules/endorsementList/endorsementList.service.ts	Updated recipient email address and name in emailCreated method and corresponding log message.

Sequence Diagram(s)

No sequence diagram generated since the changes only affect static email recipient data and log messages, without altering control flow or feature logic.

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit bf37686.

Command	Status	Duration	Result
nx run-many --projects application-system-api -...	✅ Succeeded	9m 14s	View ↗
nx run-many --target=build --projects=api --par...	✅ Succeeded	6m 12s	View ↗
nx run-many --projects application-template-api...	✅ Succeeded	5m 30s	View ↗
nx run-many --target=build --projects=applicati...	✅ Succeeded	4m 43s	View ↗
nx run-many --target=build --projects=services-...	✅ Succeeded	1m 55s	View ↗
nx run-many --projects api,api-domains-applicat...	✅ Succeeded	12s	View ↗
nx run-many -t lint --output-style=static --pro...	✅ Succeeded	1s	View ↗
nx run-many --projects services-endorsements-ap...	✅ Succeeded	4s	View ↗
Additional runs (4)	✅ Succeeded	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-05-12 13:06:22 UTC

[datadog-island-is]

Datadog Report

All test runs 01cb226 🔗

✅ 4 Total Test Services: 0 Failed, 3 Passed

Test Services

Service Name	Failed	Known Flaky	New Flaky	Passed	Skipped	Total Time	Test Service View
api	0	0	0	4	0	2.03s	Link
application-system-api	0	0	0	46	0	9m 9.85s	Link
application-template-api-modules	0	0	0	12	0	5m 25.45s	Link
services-endorsements-api	0	0	0	0	0	705.52ms	Link

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ecb67f9 and bf37686.

📒 Files selected for processing (1)

• apps/services/endorsements/api/src/app/modules/endorsementList/endorsementList.service.ts (2 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

`apps/services/**/*`: "Confirm that the code adheres to the following: - NestJS architecture, including modules, services, and controllers. - Dependency injection patterns and serv...

apps/services/**/*: "Confirm that the code adheres to the following:

• NestJS architecture, including modules, services, and controllers.
• Dependency injection patterns and service encapsulation.
• Integration and unit testing coverage and practices."

• apps/services/endorsements/api/src/app/modules/endorsementList/endorsementList.service.ts

`apps/**/*`: "Confirm that the code adheres to the following: - NextJS best practices, including file structure, API routes, and static generation methods. - Efficient state manage...

apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

• apps/services/endorsements/api/src/app/modules/endorsementList/endorsementList.service.ts

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: prepare / install