chore: Only allow for opting out of aggregate side effects in unit of work.

[MagnusSandgren]

Summary by CodeRabbit

• New Features

  • Introduced a new method for handling aggregate entities, enhancing the management of entity states during database operations.

• Bug Fixes

  • Improved error handling logic in dialog updates to ensure unexpected states are flagged appropriately.

• Refactor

  • Renamed methods and updated internal logic to focus on aggregate side effects instead of auditing.
  • Refactored filtering logic for updatable entities to improve modularity and clarity.

• Documentation

  • Updated documentation comments to reflect changes in methods and their functionalities.

[coderabbitai[bot]]

📝 Walkthrough

## Walkthrough The pull request introduces several modifications primarily focused on renaming methods and changing terminology related to side effects in the context of database operations. The method `WithoutAuditableSideEffects()` has been renamed to `WithoutAggregateSideEffects()` across multiple classes, indicating a shift in focus from auditing to aggregate-level handling of side effects. Additionally, error handling logic has been refined in various places, and new methods related to aggregate entity handling have been added, enhancing the overall functionality and maintainability of the code. ## Changes | File | Change Summary | |----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `src/Digdir.Domain.Dialogporten.Application/Externals/IUnitOfWork.cs` | Method renamed: `WithoutAuditableSideEffects()` → `WithoutAggregateSideEffects()` | | `src/Digdir.Domain.Dialogporten.Application/Features/V1/EndUser/Dialogs/Queries/Get/GetDialogQuery.cs` | Method call updated: `_unitOfWork.WithoutAuditableSideEffects()` → `_unitOfWork.WithoutAggregateSideEffects()`. Error handling logic refined for domain errors during update of `SeenAt` property. | | `src/Digdir.Domain.Dialogporten.Application/Features/V1/ServiceOwner/Dialogs/Queries/Get/GetDialogQuery.cs` | Method call updated: `WithoutAuditableSideEffects()` → `WithoutAggregateSideEffects()`. Error handling logic refined to throw `UnreachableException` for specific domain errors. | | `src/Digdir.Domain.Dialogporten.Infrastructure/UnitOfWork.cs` | Method renamed: `WithoutAuditableSideEffects()` → `WithoutAggregateSideEffects()`. Logic updated to handle aggregate entities instead of auditable ones. | | `src/Digdir.Library.Entity.EntityFrameworkCore/EntityLibraryEfCoreExtensions.cs` | Method added: `HandleAggregateEntities`. Method signature updated: `HandleAuditableEntities()` return type changed from `Task` to `ChangeTracker`. | | `src/Digdir.Library.Entity.EntityFrameworkCore/Features/Aggregate/AggregateExtensions.cs` | Method signature updated: `HandleAggregateEntities()` return type changed from `Task` to `Task`. | | `src/Digdir.Library.Entity.EntityFrameworkCore/Features/Updatable/UpdatableExtensions.cs` | Method signature updated: `HandleUpdatableEntities()` logic refactored with new methods `IsNotSoftDeleted`, `AddedWithoutExplicitUpdatedAt`, and `Modified` added for clarity and modularity. |

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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.` 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 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud