Skip to content

Commit 1de60e1

Browse files
fix: Rewrite changelog to introduce Runnable Endpoint as new feature
Per feedback from Catherine, this rewrites the changelog to introduce the component as a brand new feature rather than framing it as improvements to an existing component. Co-Authored-By: Deep Singhvi <[email protected]>
1 parent 8dee23b commit 1de60e1

File tree

1 file changed

+10
-18
lines changed

1 file changed

+10
-18
lines changed
Lines changed: 10 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,17 @@
1-
## Enhanced Runnable Endpoint Component
1+
## Introducing Runnable Endpoint
22

3-
We've improved the Runnable Endpoint component with a cleaner, more maintainable architecture and new features that make testing API endpoints even easier.
3+
Test API endpoints directly from your documentation with our new interactive component. Runnable Endpoint allows your users to send real HTTP requests to your API without leaving your docs, making it easier for developers to explore and understand your API.
44

5-
### What's New
5+
Embed the component anywhere in your MDX documentation to create an interactive request builder with form inputs for headers, path parameters, query parameters, and request bodies. Users can execute requests and see real-time responses, complete with status codes and syntax highlighting.
66

7-
**Componentized Architecture**: The Runnable Endpoint has been refactored into modular, reusable components for better maintainability and easier future enhancements.
7+
Key features include:
88

9-
**Multiple Examples Support**: When your endpoint has multiple pre-configured examples, a dropdown selector now appears in the header, making it easy to switch between different scenarios.
9+
- **Interactive form builder** that automatically generates inputs based on your endpoint definition
10+
- **Multiple examples support** with a dropdown selector when you have multiple pre-configured scenarios
11+
- **Environment selector** for testing against production, staging, or development
12+
- **Form persistence** that saves user input in local storage across sessions
13+
- **Direct navigation** to the full API reference with an "Open in API reference" button
1014

11-
**Environment Selector**: If your API defines multiple environments, users can now select which environment to test against directly from the component interface.
12-
13-
**Open in API Reference**: A new button links directly to the full API reference page for the endpoint, providing quick access to detailed documentation.
14-
15-
**Improved Form Persistence**: Form state is now automatically saved to local storage, preserving your test data across page navigation and browser sessions.
16-
17-
### Component Structure
18-
19-
The refactored component includes:
20-
- `RunnableEndpointHeader`: Endpoint URL display, example selector, and navigation controls
21-
- `RunnableEndpointFormSection`: Input forms for headers, path parameters, query parameters, and body
22-
- `RunnableEndpointActions`: Clear and send request buttons
23-
- `RunnableEndpointResponseSection`: Response preview with syntax highlighting
15+
The component is built with a modular architecture, making it maintainable and extensible for future enhancements.
2416

2517
To learn more about using Runnable Endpoints in your documentation, visit the [Runnable Endpoint docs](/learn/docs/building-and-customizing-your-docs/component-library/runnable-endpoint).

0 commit comments

Comments
 (0)