Review and refactor how dependencies are stored and exposed in `StateManager`

Open
#26,052 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
databases

Research direction

Start by examining StateManager, IStateManager, Dependencies, and InternalEntityEntry, focusing on how dependencies are stored, exposed, and consumed. Determine which dependencies are redundant and how ChangeDetector is intended to be accessed. Done means the dependency storage and exposure are consistent without unnecessary duplication.

Written by the indexing model from the issue text.

Description

area-change-tracking needs-design
  • It stores some dependencies redundantly even though they are contained in Dependencies already.
  • Dependencies is exposed on IStateManager
  • InternalEntityEntry uses ChangeDetector even though it's not exposed on IStateManager
Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.