Add persisted operations to near-operation-file

[Shane32]

Description

Adds persisted operation support to near-operation-file. Since I've no idea what I'm doing, I had Cline (Anthropic AI), copy functionality from client-preset and this is what it came up with.

Related:

• Add persistedDocuments support for other presets or add it to a plugin. #496

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Hoping someone else knows how to finish/test this PR.

Checklist:

• I have followed the
  CONTRIBUTING doc and the
  style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Further comments

Sorry, I don't know much about codegen plugins. Just hoping this PR will kick start some community progress. I will update this PR if/as I make any more progress.

At a minimum, this code could be used as a reference for issue #496

[changeset-bot]

⚠️ No Changeset found

Latest commit: 85445d8

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

[Shane32]

Cline removed this line, so I added it back as a comment. Seems like client-preset did some kind of plugin map on typed-document-node, hooking into it so that this promise would run after typed-document-node finished. Not really sure if that is applicable here or how to integrate it.

[Shane32]

For reference, here's the code from client-preset:

    const tdnFinished = createDeferred();
    const persistedDocumentsMap = new Map<string, string>();

    const pluginMap = {
      ...options.pluginMap,
      [`add`]: addPlugin,
      [`typescript`]: typescriptPlugin,
      [`typescript-operations`]: typescriptOperationPlugin,
      [`typed-document-node`]: {
        ...typedDocumentNodePlugin,
        plugin: async (...args: Parameters<PluginFunction>) => {
          try {
            return await typedDocumentNodePlugin.plugin(...args);
          } finally {
            tdnFinished.resolve();
          }
        },
      },
      [`gen-dts`]: gqlTagPlugin,
    };