Skip to content

fix: Move dispatcher inside email service #451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 3, 2025

Conversation

Lee31416
Copy link
Contributor

@Lee31416 Lee31416 commented Apr 2, 2025

GitHub Issue: #

Proposed Changes

  • Bug fix
  • Feature
  • Code style update (formatting)
  • Refactoring (no functional changes, no api changes)
  • Build or CI related changes
  • Documentation content changes
  • Other, please describe:

Description

Simply moving the dispatcher in the email service instead of where it was called for better code.

Impact on version

  • Major
    • The template structure was changed.
  • Minor
    • New functionalities were added.
  • Patch
    • A bug in behavior was fixed.
    • Documentation was changed.

PR Checklist

Always applicable

No matter your changes, these checks always apply.

  • Your conventional commits are aligned with the Impact on version section.
  • Updated CHANGELOG.md.
    • Use the latest Major.Minor.X header if you do a Patch change.
    • Create a new Major.Minor.X header if you do a Minor or Major change.
    • If you create a new header, it aligns with the Impact on version section and matches what is generated in the build pipeline.
  • Documentation files were updated according with the changes.
    • Update README.md and TemplateConfig.md if you made changes to templating.
    • Update AzurePipelines.md and APP_README.md if you made changes to pipelines.
    • Update Diagnostics.md if you made changes to diagnostic tools.
    • Update Architecture.md and its diagrams if you made architecture decisions or if you introduced new recipes.
    • ...and so forth: Make sure you update the documentation files associated to the recipes you changed. Review the topics by looking at the content of the doc/ folder.
  • Images about the template are referenced from the wiki and added as images in this git.
  • TODO comments are hints for next steps for users of the template and not planned work.

Contextual

Based on your changes these checks may not apply.

  • Automated tests for the changes have been added/updated.
  • Tested on all relevant platforms

Other information

Internal Issue (If applicable):

@Soap-141
Copy link
Contributor

Soap-141 commented Apr 3, 2025

Don't forget to fill out the PR template.

@Lee31416 Lee31416 force-pushed the dev/topi/fix-email-service branch from a9f47c7 to 4be854f Compare April 3, 2025 15:27
@Lee31416
Copy link
Contributor Author

Lee31416 commented Apr 3, 2025

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Lee31416 Lee31416 force-pushed the dev/topi/fix-email-service branch from 4be854f to 26b9801 Compare April 3, 2025 18:08
@Lee31416 Lee31416 merged commit 223f687 into main Apr 3, 2025
14 checks passed
@Lee31416 Lee31416 deleted the dev/topi/fix-email-service branch April 3, 2025 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants