fix: update docs to match actual RJSF implementation

- Remove `format: "select"` from formats table (not a distinct format)
- Add `options.documentation` to supported options (link icon with tooltip)
- Note that `options.tooltip` supports Markdown
- Fix `enumSource`/`watch` — NOT deprecated, still supported (moved to Legacy)
- Mark `links` as deprecated (not supported in RJSF), suggest `options.documentation`
- Add examples for tooltips and documentation links
- Add `options.documentation` migration example in Links section

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Mystypix

extend/component/ui-options/configuration-schema.md

@@ -39,7 +39,6 @@ The following `format` values are supported in property definitions:
 | `date` | string | Date picker input |
 | `checkbox` | boolean | Checkbox toggle |
 | `radio` | string | Radio button group (requires `enum`) |
-| `select` | array | Multi-select dropdown (with `uniqueItems: true`) |
 | `trim` | string | Standard text input with automatic whitespace trimming |
 | `grid` / `grid-strict` | object | Responsive grid layout for grouped fields |
 | `tabs` / `tabs-top` / `categories` | object | Tabbed layout for grouped fields |
@@ -59,7 +58,8 @@ The following `options` keys can be used in property definitions:
 | `options.dependencies` | Conditional field visibility based on other field values. See [Dynamic Options](/extend/component/ui-options/configuration-schema/examples/#changing-set-of-options-dynamically-based-on-selection). |
 | `options.tags` | Enable tag-style input for multi-select arrays |
 | `options.creatable` | Allow user-created values in select dropdowns |
-| `options.tooltip` | Help text displayed as a tooltip |
+| `options.tooltip` | Help text displayed as a tooltip icon next to the field label. Supports Markdown syntax. |
+| `options.documentation` | Documentation link rendered as a book icon next to the field label. Value: `{ "link": "https://...", "tooltip": "optional hover text" }` |
 | `options.enum_titles` | Display labels for `enum` values |
 | `options.hidden` | Hide the field from the UI |
 | `options.collapsed` | Start object sections in collapsed state |
@@ -143,8 +143,30 @@ The form above can be created using this JSON Schema:
 {% endhighlight %}
 
 ### Links Example
-If you want to provide links to external resources, keep in mind that the configuration schema does not support markdown,
-but it has a `links` feature. The above example can be modified so that the links are clickable:
+
+***Note:** The `links` feature is deprecated. Use `options.documentation` instead (see [Supported Options](#supported-options)).*
+
+If you want to provide links to external resources, use `options.documentation` to add a clickable documentation icon next to the field label:
+
+{% highlight json %}
+{
+    "dateFrom": {
+        "title": "Date from",
+        "type": "string",
+        "description": "Any date accepted by the strtotime function",
+        "options": {
+            "documentation": {
+                "link": "https://www.php.net/manual/en/function.strtotime.php",
+                "tooltip": "strtotime Documentation"
+            }
+        }
+    }
+}
+{% endhighlight %}
+
+#### Legacy links feature (deprecated)
+
+The old `links` property is **no longer supported**. If you have existing schemas using it, migrate to `options.documentation`:
 
 {% highlight json %}
 {
@@ -209,8 +231,14 @@ Which renders like this:
 {: .image-popup}
 ![Configuration Schema with links](/extend/component/ui-options/configuration-schema-2.png)
 
+### Legacy Features
+
+The following features are still supported for backwards compatibility but have preferred alternatives:
+
+- **`enumSource` / `watch`** — Dynamic enum population based on other field values. For new schemas, prefer `options.async` with sync actions instead. See [Sync Action Examples](/extend/component/ui-options/configuration-schema/sync-action-examples/#autoload).
+
 ### Deprecated Features
 
 The following features from the legacy JSON Editor library are **no longer supported**:
 
-- **`enumSource` / `watch`** — Dynamic enum population based on other field values. Use `options.async` with `autoload` instead for cascading dropdowns. See [Sync Action Examples](/extend/component/ui-options/configuration-schema/sync-action-examples/#autoload).
+- **`links`** — Clickable links on field descriptions. Use `options.documentation` with `link` and optional `tooltip` instead.

extend/component/ui-options/ui-examples/configuration-schema-examples.md

@@ -477,6 +477,39 @@ You can also reference nested fields using dot notation with a `root.` prefix:
 This shows the field only when the `#api_token` field inside the `credentials` object is empty.
 
 
+### Tooltips and Documentation Links
+
+Use `options.tooltip` to add a help icon next to the field label. The tooltip content supports **Markdown** syntax:
+
+```json
+{
+    "api_key": {
+        "type": "string",
+        "title": "API Key",
+        "options": {
+            "tooltip": "Your API key from the [dashboard](https://example.com/dashboard).\n\n**Note:** Keep this value secret."
+        }
+    }
+}
+```
+
+Use `options.documentation` to add a clickable documentation link icon:
+
+```json
+{
+    "query": {
+        "type": "string",
+        "title": "SQL Query",
+        "options": {
+            "documentation": {
+                "link": "https://docs.example.com/sql-reference",
+                "tooltip": "Open SQL reference"
+            }
+        }
+    }
+}
+```
+
 ### Radio Buttons
 
 Use `format: "radio"` with an `enum` to render radio buttons instead of a dropdown: