Fix code review issues: update import paths, add JSDoc, improve layout documentation

Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>

Author: Copilot

packages/plugin-object/README.md

@@ -18,7 +18,7 @@ npm install @object-ui/plugin-object @object-ui/data-objectql
 ### ObjectTable
 
 ```tsx
-import { ObjectTable } from '@object-ui/data-object';
+import { ObjectTable } from '@object-ui/plugin-object';
 import { ObjectQLDataSource } from '@object-ui/data-objectql';
 
 const dataSource = new ObjectQLDataSource({
@@ -42,7 +42,7 @@ function UsersTable() {
 ### ObjectForm
 
 ```tsx
-import { ObjectForm } from '@object-ui/data-object';
+import { ObjectForm } from '@object-ui/plugin-object';
 import { ObjectQLDataSource } from '@object-ui/data-objectql';
 
 const dataSource = new ObjectQLDataSource({

packages/plugin-object/src/ObjectForm.tsx

@@ -237,7 +237,18 @@ export const ObjectForm: React.FC<ObjectFormProps> = ({
 };
 
 /**
- * Map ObjectQL field type to form field type
+ * Maps an ObjectQL field type to the corresponding form field component type.
+ *
+ * This helper provides the translation layer between backend/ObjectQL field
+ * definitions (e.g. `text`, `date`, `lookup`) and the generic form field
+ * types understood by the schema renderer (e.g. `input`, `date-picker`,
+ * `select`). If a field type is not explicitly mapped, the function falls
+ * back to the generic `"input"` type.
+ *
+ * @param fieldType - The ObjectQL field type identifier to convert
+ * (for example: `"text"`, `"number"`, `"date"`, `"lookup"`).
+ * @returns The normalized form field type string used in the form schema
+ * (for example: `"input"`, `"textarea"`, `"date-picker"`, `"select"`).
  */
 function mapFieldTypeToFormType(fieldType: string): string {
   const typeMap: Record<string, string> = {

packages/types/src/objectql.ts

@@ -204,13 +204,31 @@ export interface ObjectFormSchema extends BaseSchema {
   }>;
 
   /**
-   * Form layout
+   * Form layout.
+   *
+   * Supported layouts:
+   * - `vertical`   – label above field (default)
+   * - `horizontal` – label and field in a row
+   * - `inline`     – compact inline layout, typically used in toolbars
+   * - `grid`       – **experimental** grid layout
+   *
+   * Note: As of the current implementation, the underlying form renderer does not yet
+   * support a native `grid` layout and will internally treat `layout: "grid"` as
+   * `layout: "vertical"`. This value is exposed in the schema for forward compatibility,
+   * and behavior may change once grid support is implemented.
+   *
    * @default 'vertical'
    */
   layout?: 'vertical' | 'horizontal' | 'inline' | 'grid';
 
   /**
-   * Grid columns (for grid layout)
+   * Grid columns (for grid layout).
+   *
+   * Intended number of columns when using a `grid` layout. Current renderers that do
+   * not implement true grid support may ignore this value and fall back to a vertical
+   * layout. When grid layout is supported, this value should control how many form
+   * fields are placed per row.
+   *
    * @default 2
    */
   columns?: number;