Skip to content

Make graphql handler reusable#1552

Open
rmn-boiko wants to merge 1 commit intomasterfrom
feat/1504-make-graphql-handler-reusable
Open

Make graphql handler reusable#1552
rmn-boiko wants to merge 1 commit intomasterfrom
feat/1504-make-graphql-handler-reusable

Conversation

@rmn-boiko
Copy link
Copy Markdown
Contributor

@rmn-boiko rmn-boiko commented Jan 14, 2026

Description

Closes: #1504

Checklist before requesting a review

@rmn-boiko rmn-boiko self-assigned this Jan 14, 2026

pub fn extend_graphql_request(
request: async_graphql::Request,
catalog: &Catalog,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Optional: &dill::Catalog

Comment on lines +20 to +22
pub struct GraphqlRequestContext {
pub extend_request: fn(async_graphql::Request, &Catalog) -> async_graphql::Request,
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Q: Can we try to avoid this dill component by currying graphql_handler() w/ some before request callback?

I mean that we call some sort of handler builder which will return the handler to us in the form of a function?

Copy link
Copy Markdown
Member

@s373r s373r left a comment

Choose a reason for hiding this comment

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

Please use sku/molecule_phase_2 as the base branch -- we need this refactoring in the near future

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.

HTTP: Make graphql_handler() handler reusable

2 participants