@domkm What's the motivation for Serene generating a spec for every enum value in an enum, instead of a single spec with enum values in a set? I've got some fairly large enums in my graphql schema and the current approach ends up generating files more than 2x bigger (a spec for each enum value in addition to its entry ni an enum spec). I'm not sure what the extra level of indirection is buying me.

bigger issue is I can't use def-specs bc I hit "method code is too large". 🙂

What is the default websockets url and port, with lacinia-pedestal in the following config:

(lp/service-map {:graphiql true
                   :port port
                   :subscriptions true})

@pri /graphql-ws

@pri I think you need to modify the default interceptors though to handle websocket connections