-
Notifications
You must be signed in to change notification settings - Fork 3
feature/AB#28576 - Tag Management Settings #1320
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
Conversation
…rvices and Permissions
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request adds a consolidated Tag Management Settings interface and implements tag-related business logic for both application tags and payment tags. Key changes include new UI-related mappings and permissions, enhanced tag sanitization and renaming logic in the application and payment services, and the addition of event handlers for tag rename and deletion.
Reviewed Changes
Copilot reviewed 34 out of 34 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| GrantManagerApplicationAutoMapperProfile.cs | Added mapping for TagSummaryCount to TagSummaryCountDto. |
| ApplicationTagsAppService.cs | Introduced tag sanitization, tag summary retrieval, rename and delete methods for application tags, and integrated local event bus notifications. |
| PaymentTagAppService.cs | Implemented similar tag management features for payment tags along with tag summary, rename, and delete support. |
| PaymentTagRepository.cs | Added repository methods for tag summary grouping and max rename length calculation. |
| PermissionDefinitionProvider.cs, UnitySelector.cs, DTOs, and event handlers | Introduced new tag management permissions and supporting types/events. |
| NotificationsSettingPageContributor.cs and its view | Updated notifications settings with minor ordering improvements. |
Comments suppressed due to low confidence (1)
applications/Unity.GrantManager/modules/Unity.Payments/src/Unity.Payments.Application/Events/RenameTagEto.cs:8
- Consider renaming 'originalTagName' (and similarly 'replacementTagName') to 'OriginalTagName' and 'ReplacementTagName' to follow standard C# property naming conventions.
public required string originalTagName { get; set; }
...ents/src/Unity.Payments.Application/EntityFrameworkCore/Repositories/PaymentTagRepository.cs
Show resolved
Hide resolved
|
Thanks Patrick very thrurough |
This pull request implements a Setting Management Interface for Tag Management:
Application and Payment Tags Management:
CreateorUpdateTagsAsyncto ensure consistent formatting of tag strings.ApplicationTagAppServiceandPaymentTagAppServicefor tag management, including tag summary retrieval, renaming, and deletion with validation and error handling.TagSummaryCountDtoandTagSummaryCountforApplicationTagsandPaymentTagsclasses to represent tag summaries, including tag name and count. [1] [2]IApplicationTagsRepositoryandIPaymentTagRepositoryand their implementations to support tag summary retrieval and maximum rename length calculation for client-side validation. [1] [2]DeleteTagHandlerandRenameTagHandlerto handle tag deletion and renaming events asynchronously and maintain modular separation. [1] [2]SettingManagement.Tagsnamespace. [1] [2]