Can we define an order in plugin execution?

kewshah4 · March 6, 2023, 3:00pm

If we have multiple plugins listening for the same lifecycle event, can define an order in their execution.
For example plugin P1, P2 and P3 all listen for didResolveSource, is there a way that we can define that P1 should complete first, then P2 and finally P3?

trevor.scheer · March 6, 2023, 5:35pm

The didResolveSource events are not individually awaited by Apollo Server so I wouldn’t structure your code in a way that depends on an order (i.e. the order of your plugins array) if you can avoid it. Do you mind sharing a bit more about what you’re trying to do?

github.com

apollographql/apollo-server/blob/d7e9b97595b063f1e796ec4449850a16d19e8b18/packages/server/src/requestPipeline.ts#L190-L196


      
          await Promise.all(
            requestListeners.map((l) =>
              l.didResolveSource?.(
                requestContext as GraphQLRequestContextDidResolveSource<TContext>,
              ),
            ),
          );

Topic		Replies	Views
ApolloServer plugin does not respond to willResolveField event Help server	2	346	September 17, 2021
Verify Apollo Server Plugin Drain Http Server is setup correctly Help server , federation	1	355	February 24, 2023
responseCachePlugin() is not a function Help server , web	4	1399	March 21, 2022
Proper way of returning errors on responseFromOperation hook? Help server	1	505	January 18, 2023
Next.js + Apollo Server SSR Help server	3	995	March 21, 2023

Can we define an order in plugin execution?

Related Topics