docs: rename annotations-reference to attributes-reference (#800)

* docs: rename annotations-reference to attributes-reference

Doctrine annotation support was dropped in #677; the page's body has
been calling these "attributes" for a long time. Bring the filename
and URL slug in line so the whole stack uses consistent terminology.

What changed
- website/docs/annotations-reference.md → attributes-reference.md
  (plus frontmatter `id` and sidebars.json entry)
- versioned_docs/version-8.0.0/ gets the same rename since 8.0.0 is
  the current stable release served at `/docs/annotations-reference`.
  Older versioned_docs are frozen snapshots and are left untouched.
- versioned_sidebars/version-8.0.0-sidebars.json updated to match.
- Incoming link in authentication-authorization.mdx updated (both
  the `next` and v8.0.0 copies).
- CHANGELOG.md and migrating.md link paths updated (both copies).
  Anchor fragments were already stale (sections were renamed from
  `## @input annotation` → `## #[Input]` long ago); repointed them at
  the current slugs where the anchor identifies the attribute
  unambiguously, and stripped the dead `-annotation` suffix.

Backwards compatibility
- Added `@docusaurus/plugin-client-redirects` (pinned to the existing
  2.4.3 line) with a single rule: `/docs/annotations-reference` →
  `/docs/attributes-reference`. External inbound links keep working
  (meta-refresh + JS redirect, preserves the URL fragment).

Remaining prose cleanup
While touching this area, also fixed a few stale "annotation" prose
references that the Doctrine removal missed:
- custom-types.mdx: "in the following annotations:" → "attributes:"
- semver.md: "through its annotations"/"custom annotations" → attributes
- argument-resolving.md: stale `@Autowire annotation` and related
  wording in the parameter-middleware example

Verified via `yarn build`: site compiles clean, redirect HTML emitted
at build/docs/annotations-reference/index.html pointing at the new
canonical URL.

* docs: revert v8.0.0 edits and cut v8.2.0 snapshot instead

Follow-up to review feedback: v8.0.0 is a frozen release snapshot and
shouldn't be edited to reflect unreleased terminology. Restore all
v8.0.0 versioned_docs files to their state at release time (matches
origin/master exactly).

Instead, cut a new v8.2.0 docs snapshot via `yarn docusaurus docs:version
8.2.0`. That captures the current `docs/` state — including the rename,
the prose cleanup, and unreleased features like #[EnumValue] (#793) —
as a new versioned release. 8.2.0 becomes the new "latest" (first in
versions.json), so `/docs/*` now serves from it and the redirect
target `/docs/attributes-reference` is valid.

Result:
- /docs/annotations-reference → redirects to /docs/attributes-reference
- /docs/attributes-reference → v8.2.0 (new latest)
- /docs/8.0.0/annotations-reference → v8.0.0 snapshot, frozen, unchanged
- /docs/next/attributes-reference → docs/ preview

Minor docs-version snapshots are established convention in this
project (6.1, 4.3, 4.2, 4.1 are all on record), so cutting 8.2.0
alongside this rename does not break norms.

Build verified: `yarn build` passes; redirect HTML emitted at
build/docs/annotations-reference/index.html; v8.0.0 snapshot diffs
to origin/master as zero.

Author: oojacoboo

website/docs/CHANGELOG.md

@@ -181,8 +181,8 @@ public function toGraphQLInputType(Type $type, ?InputType $subType, string $argu
 
 ### New features
 
-- [@Input](annotations-reference.md#input-annotation) annotation is introduced as an alternative to `#[Factory]`. Now GraphQL input type can be created in the same manner as `#[Type]` in combination with `#[Field]` - [example](input-types.mdx#input-attribute).
-- New attributes has been added to [@Field](annotations-reference.md#field-annotation) annotation: `for`, `inputType` and `description`.
+- [@Input](attributes-reference.md#input) annotation is introduced as an alternative to `#[Factory]`. Now GraphQL input type can be created in the same manner as `#[Type]` in combination with `#[Field]` - [example](input-types.mdx#input-attribute).
+- New attributes has been added to [@Field](attributes-reference.md#field) annotation: `for`, `inputType` and `description`.
 - The following annotations now can be applied to class properties directly: `#[Field]`, `#[Logged]`, `#[Right]`, `@FailWith`, `@HideIfUnauthorized` and `#[Security]`.
 
 ## 4.1.0

website/docs/argument-resolving.md

@@ -60,7 +60,7 @@ If you plan to use attributes while resolving arguments, your attribute class sh
 
 For instance, if we want GraphQLite to inject a service in an argument, we can use `#[Autowire]`.
 
-We only need to put declare the annotation can target parameters: `#[Attribute(Attribute::TARGET_PARAMETER)]`.
+We only need to declare that the attribute can target parameters: `#[Attribute(Attribute::TARGET_PARAMETER)]`.
 
 The class looks like this:
 
@@ -106,16 +106,16 @@ class ContainerParameterHandler implements ParameterMiddlewareInterface
 
     public function mapParameter(ReflectionParameter $parameter, DocBlock $docBlock, ?Type $paramTagType, ParameterAnnotations $parameterAnnotations, ParameterHandlerInterface $next): ParameterInterface
     {
-        // The $parameterAnnotations object can be used to fetch any annotation implementing ParameterAnnotationInterface
+        // The $parameterAnnotations object can be used to fetch any attribute implementing ParameterAnnotationInterface
         $autowire = $parameterAnnotations->getAnnotationByType(Autowire::class);
 
         if ($autowire === null) {
-            // If there are no annotation, this middleware cannot handle the parameter. Let's ask
+            // If there is no matching attribute, this middleware cannot handle the parameter. Let's ask
             // the next middleware in the chain (using the $next object)
             return $next->mapParameter($parameter, $docBlock, $paramTagType, $parameterAnnotations);
         }
 
-        // We found a @Autowire annotation, let's return a parameter resolver.
+        // We found a #[Autowire] attribute, let's return a parameter resolver.
         return new ContainerParameter($this->container, $parameter->getType());
     }
 }

website/docs/annotations-reference.md website/docs/attributes-reference.mdwebsite/docs/annotations-reference.md renamed to website/docs/attributes-reference.md

@@ -1,5 +1,5 @@
 ---
-id: annotations-reference
+id: attributes-reference
 title: Attributes reference
 sidebar_label: Attributes reference
 ---

website/docs/authentication-authorization.mdx

@@ -130,7 +130,7 @@ By default, a user analysing the GraphQL schema can see all queries/mutations/su
 Some will be available to him and some won't.
 
 If you want to add an extra level of security (or if you want your schema to be kept secret to unauthorized users),
-you can use the `#[HideIfUnauthorized]` attribute. Beware of [it's limitations](annotations-reference.md).
+you can use the `#[HideIfUnauthorized]` attribute. Beware of [it's limitations](attributes-reference.md).
 
 ```php
 class UserController

website/docs/custom-types.mdx

@@ -41,7 +41,7 @@ You can help GraphQLite by manually specifying the output type to use:
 
 The `outputType` attribute will map the return value of the method to the output type passed in parameter.
 
-You can use the `outputType` attribute in the following annotations:
+You can use the `outputType` attribute in the following attributes:
 
 * `#[Query]`
 * `#[Mutation]`

website/docs/migrating.md

@@ -32,7 +32,7 @@ If you are a "regular" GraphQLite user, migration to v4 should be straightforwar
 - In GraphQLite v3, the default was to hide a field from the schema if a user has no access to it.
   In GraphQLite v4, the default is to still show this field, but to throw an error if the user makes a query on it
   (this way, the schema is the same for all users). If you want the old mode, use the new
-  [`@HideIfUnauthorized` annotation](annotations-reference.md#hideifunauthorized-annotation)
+  [`@HideIfUnauthorized` annotation](attributes-reference.md#hideifunauthorized)
 - If you are using the Symfony bundle, the Laravel package or the Universal module, you must also upgrade those to 4.0.
   These package will take care of the wiring for you. Apart for upgrading the packages, you have nothing to do.
 - If you are relying on the `SchemaFactory` to bootstrap GraphQLite, you have nothing to do.

website/docs/semver.md

@@ -16,8 +16,8 @@ To avoid being bound to our backward compatibility promise, such features can be
 
 As a rule of thumb:
 
-- If you are a GraphQLite user (using GraphQLite mainly through its annotations), we guarantee strict semantic versioning
-- If you are extending GraphQLite features (if you are developing custom annotations, or if you are developing a GraphQlite integration
+- If you are a GraphQLite user (using GraphQLite mainly through its attributes), we guarantee strict semantic versioning
+- If you are extending GraphQLite features (if you are developing custom attributes, or if you are developing a GraphQlite integration
   with a framework...), be sure to check the tags.
 
 Said otherwise:

website/docusaurus.config.js

@@ -50,7 +50,19 @@ module.exports={
       }
     ]
   ],
-  "plugins": [],
+  "plugins": [
+    [
+      "@docusaurus/plugin-client-redirects",
+      {
+        "redirects": [
+          {
+            "from": "/docs/annotations-reference",
+            "to": "/docs/attributes-reference"
+          }
+        ]
+      }
+    ]
+  ],
   "themeConfig": {
     "navbar": {
       "title": "GraphQLite",

website/package.json

@@ -9,6 +9,7 @@
   "devDependencies": {},
   "dependencies": {
     "@docusaurus/core": "2.4.3",
+    "@docusaurus/plugin-client-redirects": "2.4.3",
     "@docusaurus/preset-classic": "2.4.3",
     "clsx": "^1.1.1",
     "mdx-mermaid": "^1.2.3",

website/sidebars.json

@@ -51,7 +51,7 @@
     ],
     "Reference": [
       "doctrine-annotations-attributes",
-      "annotations-reference",
+      "attributes-reference",
       "semver",
       "changelog"
     ]