ChilliCream / ChilliCream/graphql-platform

Add an abstraction for resolving an executable

Open
#8,070 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🌶️ hot chocolate Area: Data
Dominant language
C#
Stars
5.8k
Forks
810
Avg merge
15h 39m
Merged PRs (30d)
98

Description

Product

Hot Chocolate

Is your feature request related to a problem?

An example of the problem can be found in https://github.com/ChilliCream/graphql-platform/pull/6833#issuecomment-2675535475.

The solution you'd like

From Michael, something like:

public interface IExecutableResolver
{
    IExecutable<T> Resolve<T>(object source);
}

Registered in the DI container, this would allow for middleware like the SingleOrDefaultMiddleware to execute SingleOrDefaultAsync on the appropriate IExecutable<T> implementation (f.e. EfQueryableExecutable<T>).

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.

Research direction

Start by reading the SingleOrDefaultMiddleware context and the existing IExecutable implementations, especially EfQueryableExecutable, then inspect how services are registered in the DI container. Done means introducing a resolver abstraction that selects the appropriate executable implementation for a source and allows SingleOrDefaultAsync to run through it, with tests covering the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.