microsoft / microsoft/sqlmanagementobjects
Move reflection and dynamic code invocation out of SqlSmoObject
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Start with the implementation of InitObjectsFromEnumResultsRec
Can it be a static function in separate class altogether?
We want to isolate the Sfc and reflection dependencies into a new code file whose implementation could be replaced by a C# source generator in the future. The generated code would use the Sfc attributes at compile time to build the method lookup tables.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the implementation of InitObjectsFromEnumResultsRec and trace its reflection, dynamic invocation, and Sfc dependencies. Separate that implementation into a new class or code file while preserving the method lookup behavior and leaving a boundary that could later be replaced by generated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100