make useEngine plugin the only way to pass engine functions

[saihaj]

makes user pass the useEngine plugin as the only way to set engine functions.

- import { envelop } from '@envelop/core';
+ import { envelop, useEngine } from '@envelop/core';
+ import { parse, validate, execute, subscribe } from 'graphql';

- const getEnveloped = envelop([ ... ])
+ const getEnveloped = envelop({ plugins: [ useEngine({ parse, validate, execute, subscribe }), ... ] })

[changeset-bot]

⚠️ No Changeset found

Latest commit: 58c5e6c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
envelop	✅ Ready (Inspect)	Visit Preview	Sep 26, 2022 at 1:23PM (UTC)

[enisdenjo]

One benefit of having the GQL functions as root options is type safety - if you just envelop() you'll get a TS error complaining about the missing engine functions.

How does this get tackled with the new useEngine plugin? Envelop instantly errors out if useEngine is missing? Required plugin?

[saihaj]

Envelop instantly errors out if useEngine is missing?

with current implementation you will start getting runtime errors. Like parse is missing. Provide useEngine. I did try doing a required engine plugin but the problem with that is when you are composing envelops some may not even need to provide the engine.