fix: Apply prettier formatting to README and validation.ts

Author: emdashcodes

.github/workflows/js-lint.yml

@@ -168,4 +168,4 @@ jobs:
           echo "- ESLint: ${{ needs.eslint.result }}"
           echo "- Prettier: ${{ needs.prettier.result }}"
           echo "- TypeScript: ${{ needs.typecheck.result }}"
-          exit 1
+          exit 1

packages/client/README.md

@@ -4,11 +4,11 @@ Client library for the WordPress Abilities API, providing a standardized way to
 
 ## Table of Contents
 
-- [Installation](#installation)
-- [Usage](#usage)
-- [API Reference](#api-reference)
-- [Development](#development)
-- [Testing](#testing)
+-   [Installation](#installation)
+-   [Usage](#usage)
+-   [API Reference](#api-reference)
+-   [Development](#development)
+-   [Testing](#testing)
 
 ## Installation
 
@@ -67,13 +67,13 @@ const { listAbilities, getAbility, executeAbility } = wp.abilities;
 const abilities = await listAbilities();
 
 // Get a specific ability
-const ability = await getAbility( 'my-plugin/my-ability' );
+const ability = await getAbility('my-plugin/my-ability');
 
 // Execute an ability
-const result = await executeAbility( 'my-plugin/my-ability', {
-    param1: 'value1',
-    param2: 'value2'
-} );
+const result = await executeAbility('my-plugin/my-ability', {
+	param1: 'value1',
+	param2: 'value2',
+});
 ```
 
 ### Using with React and WordPress Data
@@ -85,28 +85,28 @@ import { useSelect } from '@wordpress/data';
 import { store as abilitiesStore } from '@wordpress/abilities';
 
 function MyComponent() {
-    const abilities = useSelect(
-        ( select ) => select( abilitiesStore ).getAbilities(),
-        []
-    );
-
-    const specificAbility = useSelect(
-        ( select ) => select( abilitiesStore ).getAbility( 'my-plugin/my-ability' ),
-        []
-    );
-
-    return (
-        <div>
-            <h2>All Abilities</h2>
-            <ul>
-                { abilities.map( ( ability ) => (
-                    <li key={ ability.name }>
-                        <strong>{ ability.label }</strong>: { ability.description }
-                    </li>
-                ) ) }
-            </ul>
-        </div>
-    );
+	const abilities = useSelect(
+		(select) => select(abilitiesStore).getAbilities(),
+		[]
+	);
+
+	const specificAbility = useSelect(
+		(select) => select(abilitiesStore).getAbility('my-plugin/my-ability'),
+		[]
+	);
+
+	return (
+		<div>
+			<h2>All Abilities</h2>
+			<ul>
+				{abilities.map((ability) => (
+					<li key={ability.name}>
+						<strong>{ability.label}</strong>: {ability.description}
+					</li>
+				))}
+			</ul>
+		</div>
+	);
 }
 ```
 
@@ -120,46 +120,46 @@ Returns all registered abilities. Automatically handles pagination to fetch all
 
 ```javascript
 const abilities = await listAbilities();
-console.log( `Found ${abilities.length} abilities` );
+console.log(`Found ${abilities.length} abilities`);
 ```
 
 #### `getAbility(name: string): Promise<Ability | null>`
 
 Returns a specific ability by name, or null if not found.
 
 ```javascript
-const ability = await getAbility( 'my-plugin/create-post' );
-if ( ability ) {
-    console.log( `Found ability: ${ability.label}` );
+const ability = await getAbility('my-plugin/create-post');
+if (ability) {
+	console.log(`Found ability: ${ability.label}`);
 }
 ```
 
 #### `executeAbility(name: string, input?: Record<string, any>): Promise<any>`
 
 Executes an ability with optional input parameters. The HTTP method is automatically determined based on the ability's type:
 
-- `resource` type abilities use GET (read-only operations)
-- `tool` type abilities use POST (write operations)
+-   `resource` type abilities use GET (read-only operations)
+-   `tool` type abilities use POST (write operations)
 
 ```javascript
 // Execute a resource ability (GET)
-const data = await executeAbility( 'my-plugin/get-data', {
-    id: 123
-} );
+const data = await executeAbility('my-plugin/get-data', {
+	id: 123,
+});
 
 // Execute a tool ability (POST)
-const result = await executeAbility( 'my-plugin/create-item', {
-    title: 'New Item',
-    content: 'Item content'
-} );
+const result = await executeAbility('my-plugin/create-item', {
+	title: 'New Item',
+	content: 'Item content',
+});
 ```
 
 ### Store Selectors
 
 When using with `@wordpress/data`:
 
-- `getAbilities()` - Returns all abilities from the store
-- `getAbility(name)` - Returns a specific ability from the store
+-   `getAbilities()` - Returns all abilities from the store
+-   `getAbility(name)` - Returns a specific ability from the store
 
 ## Development
 
@@ -201,7 +201,7 @@ npm run test:unit:debug
 
 Tests are organized following WordPress conventions:
 
-- Unit tests are located in `src/__tests__/`
-- Store tests are located in `src/store/__tests__/`
-- Test files use `.test.ts` or `.test.js` extension
-- Tests use Jest with `@wordpress/jest-preset-default` configuration
+-   Unit tests are located in `src/__tests__/`
+-   Store tests are located in `src/store/__tests__/`
+-   Test files use `.test.ts` or `.test.js` extension
+-   Tests use Jest with `@wordpress/jest-preset-default` configuration