-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
# imports / Document parsing middleware #49
Comments
For reference, the output of
|
Hey @micimize! Actually the decision to make Artemis use synthetic lib input rather than iterating over each file was done exactly for grouped files parsing, I just didn't had the time to start coding those uses yet. What do you feel about having a configurable interceptor list on each About |
@comigor That seems like an alright approach - I don't follow the "builder builder" part entirely, as I'm not familiar with The "grouped file parsing" sounds like it's enough to solve my particular issue though. I think a builtin |
Currently working on a simple concatenation option for schema map, as well as looking into #30 |
I have a WIP branch for processors (just pushed it), but it may take some time to land. I'm now starting to work on how to call this generated builder code from the current builder, with the needed input, output and artemis configuration parameters. |
@comigor any progress on middleware? |
Sorry, I didn't have time to focus on it yet. |
I'd like to use
gql
'sast.transform
to implement an inline imports handler similar tographql-import
orgraphql-import-loader
, but would need a parser middleware hook to use it with artemis.Alternatives:
artemis
nativelyThe text was updated successfully, but these errors were encountered: