Fix list in generated doc (#1434)

src/Input/CreateResolverRequest.php

@@ -73,7 +73,6 @@ final class CreateResolverRequest extends Input
      *
      * - **UNIT**: A UNIT resolver type. A UNIT resolver is the default resolver type. You can use a UNIT resolver to run a
      *   GraphQL query against a single data source.
-     * -
      * - **PIPELINE**: A PIPELINE resolver type. You can use a PIPELINE resolver to invoke a series of `Function` objects in
      *   a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.
      *

src/Input/UpdateResolverRequest.php

@@ -73,7 +73,6 @@ final class UpdateResolverRequest extends Input
      *
      * - **UNIT**: A UNIT resolver type. A UNIT resolver is the default resolver type. You can use a UNIT resolver to run a
      *   GraphQL query against a single data source.
-     * -
      * - **PIPELINE**: A PIPELINE resolver type. You can use a PIPELINE resolver to invoke a series of `Function` objects in
      *   a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.
      *

src/ValueObject/ApiKey.php

@@ -12,33 +12,24 @@
  * be used.
  *
  * - `ListApiKeys` returns the expiration time in milliseconds.
- * -
  * - `CreateApiKey` returns the expiration time in milliseconds.
- * -
  * - `UpdateApiKey` is not available for this key version.
- * -
  * - `DeleteApiKey` deletes the item from the table.
- * -
  * - Expiration is stored in DynamoDB as milliseconds. This results in a bug where keys are not automatically deleted
  *   because DynamoDB expects the TTL to be stored in seconds. As a one-time action, we deleted these keys from the
  *   table on February 21, 2018.
  *
  * **da2**: We introduced this version in February 2018 when AppSync added support to extend key expiration.
  *
  * - `ListApiKeys` returns the expiration time and deletion time in seconds.
- * -
  * - `CreateApiKey` returns the expiration time and deletion time in seconds and accepts a user-provided expiration time
  *   in seconds.
- * -
  * - `UpdateApiKey` returns the expiration time and and deletion time in seconds and accepts a user-provided expiration
  *   time in seconds. Expired API keys are kept for 60 days after the expiration time. You can update the key expiration
  *   time as long as the key isn't deleted.
- * -
  * - `DeleteApiKey` deletes the item from the table.
- * -
  * - Expiration is stored in DynamoDB as seconds. After the expiration time, using the key to authenticate will fail.
  *   However, you can reinstate the key before deletion.
- * -
  * - Deletion is stored in DynamoDB as seconds. The key is deleted after deletion time.
  */
 final class ApiKey

src/ValueObject/DataSource.php

@@ -28,21 +28,14 @@ final class DataSource
      * The type of the data source.
      *
      * - **AWS_LAMBDA**: The data source is an Lambda function.
-     * -
      * - **AMAZON_DYNAMODB**: The data source is an Amazon DynamoDB table.
-     * -
      * - **AMAZON_ELASTICSEARCH**: The data source is an Amazon OpenSearch Service domain.
-     * -
      * - **AMAZON_OPENSEARCH_SERVICE**: The data source is an Amazon OpenSearch Service domain.
-     * -
      * - **AMAZON_EVENTBRIDGE**: The data source is an Amazon EventBridge configuration.
-     * -
      * - **NONE**: There is no data source. Use this type when you want to invoke a GraphQL operation without connecting to
      *   a data source, such as when you're performing data transformation with resolvers or invoking a subscription from a
      *   mutation.
-     * -
      * - **HTTP**: The data source is an HTTP endpoint.
-     * -
      * - **RELATIONAL_DATABASE**: The data source is a relational database.
      */
     private $type;

src/ValueObject/Resolver.php

@@ -44,7 +44,6 @@ final class Resolver
      *
      * - **UNIT**: A UNIT resolver type. A UNIT resolver is the default resolver type. You can use a UNIT resolver to run a
      *   GraphQL query against a single data source.
-     * -
      * - **PIPELINE**: A PIPELINE resolver type. You can use a PIPELINE resolver to invoke a series of `Function` objects in
      *   a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.
      */

src/ValueObject/SyncConfig.php

@@ -18,9 +18,7 @@ final class SyncConfig
      *
      * - **OPTIMISTIC_CONCURRENCY**: Resolve conflicts by rejecting mutations when versions don't match the latest version
      *   at the server.
-     * -
      * - **AUTOMERGE**: Resolve conflicts with the Automerge conflict resolution strategy.
-     * -
      * - **LAMBDA**: Resolve conflicts with an Lambda function supplied in the `LambdaConflictHandlerConfig`.
      */
     private $conflictHandler;
@@ -29,7 +27,6 @@ final class SyncConfig
      * The Conflict Detection strategy to use.
      *
      * - **VERSION**: Detect conflicts based on object versions for this resolver.
-     * -
      * - **NONE**: Do not detect conflicts when invoking this resolver.
      */
     private $conflictDetection;