Skip to content
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

fix(app): Add dedicated scope and dbcontext to GetSubjectResources #1648

Merged
merged 4 commits into from
Jan 6, 2025

Conversation

knuhau
Copy link
Collaborator

@knuhau knuhau commented Jan 3, 2025

Add dedicated scope and dbcontext to GetSubjectResources to avoid concurrency errors

Description

Related Issue(s)

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

  • Documentation is updated (either in docs-directory, Altinnpedia or a separate linked PR in altinn-studio-docs., if applicable)

@knuhau knuhau requested a review from a team as a code owner January 3, 2025 13:07
Copy link
Contributor

coderabbitai bot commented Jan 3, 2025

📝 Walkthrough

Walkthrough

The pull request modifies the AltinnAuthorizationClient class in the infrastructure layer by introducing a new dependency, IServiceScopeFactory, to the constructor. This change allows the class to create service scopes for dependency injection. The GetAllSubjectResources method is updated to utilize this service scope for retrieving DialogDbContext, ensuring proper management and disposal of the database context. The constructor's signature is also updated to accommodate the new parameter, along with adjustments in null value handling.

Changes

File Change Summary
src/Digdir.Domain.Dialogporten.Infrastructure/Altinn/Authorization/AltinnAuthorizationClient.cs - Added IServiceScopeFactory as a new constructor parameter
- Updated constructor to handle the new dependency
- Modified GetAllSubjectResources method to use service scope for DialogDbContext retrieval

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ae445bb and f49dffe.

📒 Files selected for processing (1)
  • src/Digdir.Domain.Dialogporten.Infrastructure/Altinn/Authorization/AltinnAuthorizationClient.cs (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/Digdir.Domain.Dialogporten.Infrastructure/Altinn/Authorization/AltinnAuthorizationClient.cs

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
🪧 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.

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. (Beta)
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1486da6 and 0b0672b.

📒 Files selected for processing (1)
  • src/Digdir.Domain.Dialogporten.Infrastructure/Altinn/Authorization/AltinnAuthorizationClient.cs (5 hunks)
🔇 Additional comments (4)
src/Digdir.Domain.Dialogporten.Infrastructure/Altinn/Authorization/AltinnAuthorizationClient.cs (4)

13-15: Imports introduced for persistence and service scope creation
The new using statements for Digdir.Domain.Dialogporten.Infrastructure.Persistence and Microsoft.Extensions.DependencyInjection appear correct and necessary for the newly introduced scope factory and DialogDbContext.


32-32: Acknowledgment: Adding _serviceScopeFactory
Introducing a private read-only field for the scope factory is a good approach for managing scoped dependencies (e.g., DialogDbContext) within the client.


45-46: Constructor update to inject IServiceScopeFactory
Including the IServiceScopeFactory parameter in the constructor ensures the necessary resources are obtained for the new scoped usage. This aligns with dependency injection best practices.


55-55: Null check for serviceScopeFactory
The null check promotes good defensive coding. Nothing else needed here.

oskogstad
oskogstad previously approved these changes Jan 6, 2025
Copy link

sonarqubecloud bot commented Jan 6, 2025

@knuhau knuhau merged commit d1040e4 into main Jan 6, 2025
25 checks passed
@knuhau knuhau deleted the fix/own-scope-dbcontext-for-GetAllSubjectResources branch January 6, 2025 09:26
oskogstad pushed a commit that referenced this pull request Jan 7, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.43.0](v1.42.1...v1.43.0)
(2025-01-07)


### Features

* Add additional types to DialogActivity
([#1629](#1629))
([feb1347](feb1347))


### Bug Fixes

* **app:** Add dedicated scope and dbcontext to GetSubjectResources
([#1648](#1648))
([d1040e4](d1040e4))
* revert azure monitor workspace
([#1624](#1624))
([d66b155](d66b155))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

3 participants