Skip to content

Commit

Permalink
remove vestigial connector preview errors (#3170)
Browse files Browse the repository at this point in the history 
these errors are technically in fed 2.7 but were removed for 2.9 and
beyond. we never formally documented the directives that would trigger
them so they can be removed.

<!--
First, 🌠 thank you 🌠 for taking the time to consider a contribution to
Apollo!

Here are some important details to follow:

* ⏰ Your time is important
To save your precious time, if the contribution you are making will
take more than an hour, please make sure it has been discussed in an
        issue first. This is especially true for feature requests!

* 💡 Features
Feature requests can be created and discussed within a GitHub Issue.
Be sure to search for existing feature requests (and related issues!)
prior to opening a new request. If an existing issue covers the need,
please upvote that issue by using the 👍 emote, rather than opening a
        new issue.

* 🕷 Bug fixes
These can be created and discussed in this repository. When fixing a
bug,
please _try_ to add a test which verifies the fix. If you cannot, you
should
still submit the PR but we may still ask you (and help you!) to create a
test.

* Federation versions
Please make sure you're targeting the federation version you're opening
the PR for. Federation 2 (alpha) is currently located on the `main`
branch and prior versions of Federation live on the `version-0.x`
branch.

* 📖 Contribution guidelines
Follow
https://github.com/apollographql/federation/blob/HEAD/CONTRIBUTING.md
when submitting a pull request. Make sure existing tests still pass, and
add
        tests for all new behavior.

* ✏️ Explain your pull request
Describe the big picture of your changes here to communicate to what
        your pull request is meant to accomplish. Provide 🔗 links 🔗 to
        associated issues!

We hope you will find this to be a positive experience! Open source
contribution can be intimidating and we hope to alleviate that pain as
much
as possible. Without following these guidelines, you may be missing
context
that can help you succeed with your contribution, which is why we
encourage
discussion first. Ultimately, there is no guarantee that we will be able
to
merge your pull-request, but by following these guidelines we can try to
avoid disappointment.

-->
  • Loading branch information
@lennyburdette
lennyburdette authored Oct 17, 2024
1 parent 4c6c268 commit 3675afe
Showing 1 changed file with 0 additions and 266 deletions.
266 changes: 0 additions & 266 deletions docs/source/errors.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1021,272 +1021,6 @@ A shareable field return type has mismatched possible runtime types in the subgr
<tr>
<td>

##### `SOURCE_API_HTTP_BASE_URL_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceAPI` directive must specify a valid http.baseURL.

</td>
</tr>
<tr>
<td>

##### `SOURCE_API_NAME_INVALID`

Since v2.7.0

</td>
<td>

Each `@sourceAPI` directive must take a unique and valid name as an argument.

</td>
</tr>
<tr>
<td>

##### `SOURCE_API_PROTOCOL_INVALID`

Since v2.7.0

</td>
<td>

Each `@sourceAPI` directive must specify exactly one of the known protocols.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FEDERATION_VERSION_REQUIRED`

Since v2.7.1

</td>
<td>

Schemas using `@source{API,Type,Field}` directives must `@link`-import v2.7 or later of Federation.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_API_ERROR`

Since v2.7.0

</td>
<td>

The `api` argument of the `@sourceField` directive must match a valid `@sourceAPI` name.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_HTTP_BODY_INVALID`

Since v2.7.0

</td>
<td>

If `@sourceField` specifies http.body, it must be a valid `JSONSelection` matching available arguments and fields.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_HTTP_METHOD_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceField` directive must specify at most one of `http.{GET,POST,PUT,PATCH,DELETE}`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_HTTP_PATH_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceField` directive must specify a valid URL template for `http.{GET,POST,PUT,PATCH,DELETE}`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_NOT_ON_ROOT_OR_ENTITY_FIELD`

Since v2.7.0

</td>
<td>

The `@sourceField` directive must be applied to a field of the `Query` or `Mutation` types, or of an entity type.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_PROTOCOL_INVALID`

Since v2.7.0

</td>
<td>

If `@sourceField` specifies a protocol, it must match the corresponding `@sourceAPI` protocol.

</td>
</tr>
<tr>
<td>

##### `SOURCE_FIELD_SELECTION_INVALID`

Since v2.7.0

</td>
<td>

The `selection` argument of the `@sourceField` directive must be a valid `JSONSelection` that outputs fields of the GraphQL type.

</td>
</tr>
<tr>
<td>

##### `SOURCE_HTTP_HEADERS_INVALID`

Since v2.7.0

</td>
<td>

The `http.headers` argument of `@source*` directives must specify valid HTTP headers.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_API_ERROR`

Since v2.7.0

</td>
<td>

The `api` argument of the `@sourceType` directive must match a valid `@sourceAPI` name.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_HTTP_BODY_INVALID`

Since v2.7.0

</td>
<td>

If the `@sourceType` specifies `http.body`, it must be a valid `JSONSelection`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_HTTP_METHOD_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceType` directive must specify exactly one of `http.GET` or `http.POST`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_HTTP_PATH_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceType` directive must specify a valid URL template for `http.GET` or `http.POST`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_ON_NON_OBJECT_OR_NON_ENTITY`

Since v2.7.0

</td>
<td>

The `@sourceType` directive must be applied to an object or interface type that also has `@key`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_PROTOCOL_INVALID`

Since v2.7.0

</td>
<td>

The `@sourceType` directive must specify the same protocol as its corresponding `@sourceAPI`.

</td>
</tr>
<tr>
<td>

##### `SOURCE_TYPE_SELECTION_INVALID`

Since v2.0.0

</td>
<td>

The `selection` argument of the `@sourceType` directive must be a valid `JSONSelection` that outputs fields of the GraphQL type.

</td>
</tr>
<tr>
<td>

##### `TYPE_DEFINITION_INVALID`

Since v2.0.0
Expand Down

0 comments on commit 3675afe

Please sign in to comment.