mirror of
https://github.com/usebruno/bruno.git
synced 2026-06-15 03:41:28 +00:00
* feat: enhance Bru grammar to support response blocks and examples - Added new grammar rules for response headers, status, and body types (JSON, XML, text). - Introduced parsing logic for example blocks, allowing multiple examples with various body types. - Implemented tests for example parsing, including edge cases and complex examples with authentication. - Created fixture files for simple and complex examples to validate parsing functionality. feat: extend jsonToBru functionality to support response handling and examples - Updated jsonToBru to include parsing for response headers, status, and body types (JSON, XML, text). - Enhanced example handling to support multiple examples with various body types. - Added comprehensive tests for example parsing, including edge cases and complex scenarios with authentication. - Created fixture files for testing the new features and validating parsing functionality. move: files to fixtures folder refactor: simplify response body handling in Bru grammar and JSON conversion - Removed specific body type handling (JSON, XML, text) from grammar and semantics. - Updated response body parsing in jsonToBru to handle a unified response body format. - Adjusted tests and fixtures to reflect changes in response body structure, ensuring compatibility with the new format. feat: add response bookmarking functionality to ResponsePane - Introduced ResponseBookmark component to allow users to save responses as examples. - Added NameExampleModal for naming saved examples. - Updated ResponsePane to include the new bookmarking feature. - Implemented Redux actions to manage response examples in the collections state. - Enhanced CollectionItem to display saved examples and allow for expansion. fix: remove unnecessary padding from ExampleItem component feat: implement delete and rename functionality for examples in ExampleItem component - Added DeleteExampleModal for confirming deletion of examples. - Integrated modal for renaming examples with state management. - Enhanced ExampleItem to handle example deletion and renaming through modals. - Updated Redux actions to support example updates and deletions in the collections state. fix: example writing to disc properly fix: example parsing errors fix: request with example parsing error fix: handle examples in collections and requests feat: implement response example functionality in the application - Added ResponseExample component to handle displaying and editing response examples. - Integrated ResponseExampleRequestPane and ResponseExampleResponsePane for structured request and response handling. - Enhanced RequestTabPanel and RequestTab components to support response-example tabs. - Introduced new styled components for better UI/UX in response examples. - Updated theme files to include styles for response examples. - Implemented URL bar for editing request URLs in response examples. - Added functionality for managing headers and parameters in response examples. - Improved overall structure and organization of response example components. add styles for example url bar feat: add Checkbox component and Table-v2 for enhanced UI - Introduced a new Checkbox component for better user interaction in forms. - Added Table-v2 component to improve table rendering and resizing functionality. - Updated existing components to utilize the new Checkbox and Table-v2 for managing headers and parameters in response examples. - Enhanced styling for better visual consistency across components. - Updated theme files to include styles for the new components. feat: implement custom scrollbar styles for response example components fix: features add actions , view more feat: enhance response example functionality - Added GenerateCodeItem component for generating code snippets from response examples. - Integrated modal for code generation within ResponseExample component. - Updated ResponseExampleTopBar to handle example name and description editing. - Improved state management for response examples, including new actions for updating names and descriptions. - Enhanced ResponseExampleRequestPane to support editing and saving request details. - Refactored URL handling in ResponseExampleUrlBar to utilize example-specific data. - Improved overall user experience with better UI elements and state management. feat: enhance response example management and UI components feat: enhance editing capabilities in response example components feat: update multipart form parameter handling in response examples feat: refactor response example parameter handling and enhance UI interactions feat: introduce RadioButton component and update Checkbox usage in response examples fix: styles fix radio button styling fixed radio button styles feat: add create example from sidebar feat: enhance ResponseExample components with layout adjustments and new HeightBoundContainer feat: add Checkbox and RadioButton components with comprehensive tests for rendering, user interactions, and accessibility feat: playwright test csaes rm: comments fix: linting fix: tests refactor: update response example tests and enhance functionality fix: tests fix: e2e-tests refactor: implement hasRequestChanges utility for better change detection rm: console rm: consoles fix: lint fix: tests fix: response header disabled by default issue Feat/with bru example parser (#5892) * fix: response header disabled by default issue feat: new parsing logic fix: change test cases to accomodate new brulang add: path params features rm:consoles six: make tab permanent on double click fix width feat: add status editing feat: review fixes review fixes fix: review fixes fix: post review mv: test files fix: review * fix: lint * fix: review comments * fix: icons folder strcuture fix: tests fix: lint fix: unit tests feat: body mode selector fix: close all collections rm: example feat added tests. lang change feat: add custom status text fix: status update feat: add body mode, update tests add default name prefilled for example fix: active tab styles, prefilled name, text fixes fix : pkg lock fix: review fix: review comments fix: hide cursor when readonly fix: height fix: null body fix: response body parsing fix: test cases feat: add method support for examples fix: reponse parsing fix: update response body type when content type is updated rm : commented code feat: update parser logic fix: organize files feat: enhance examples handling in collection export and import feat: postman imports fro examples feat: enhance OpenAPI import functionality to support examples feat: support postman export fix: postman export import fix: open api tests, remove requestbody related logic rm: examples fix: move common attributes files ui fixes fix: clone issue fix: create example from request menu review fixes more review fixes mv: files, fix mode req error organize files fix:tests fix: save dot issue fix: bugs fix: postman export fix: import path params * chore:improve modal handling in environment and response example tests fix: test issues resolved * chore: update response example tests to use new fixture files and improve cleanup logic --------- Co-authored-by: Abhishek S Lal <abhishek@usebruno.com> Co-authored-by: Bijin Bruno <bijin@usebruno.com>
156 lines
4.9 KiB
YAML
156 lines
4.9 KiB
YAML
openapi: '3.0.0'
|
|
info:
|
|
version: '1.0.0'
|
|
title: 'API with Examples'
|
|
description: 'A sample API with response examples'
|
|
servers:
|
|
- url: 'https://api.example.com'
|
|
description: 'Production server'
|
|
paths:
|
|
/users:
|
|
get:
|
|
summary: 'Get all users'
|
|
operationId: 'getUsers'
|
|
responses:
|
|
'200':
|
|
description: 'Successful response'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
success:
|
|
summary: 'Success Response'
|
|
description: 'A successful response with user data'
|
|
value:
|
|
users:
|
|
- id: 1
|
|
name: 'John Doe'
|
|
email: 'john@example.com'
|
|
- id: 2
|
|
name: 'Jane Smith'
|
|
email: 'jane@example.com'
|
|
empty:
|
|
summary: 'Empty Response'
|
|
description: 'No users found'
|
|
value:
|
|
users: []
|
|
'400':
|
|
description: 'Bad Request'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
validation_error:
|
|
summary: 'Validation Error'
|
|
description: 'Invalid request parameters'
|
|
value:
|
|
error: 'Invalid parameters'
|
|
message: 'The request contains invalid data'
|
|
code: 'VALIDATION_ERROR'
|
|
'500':
|
|
description: 'Internal Server Error'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
server_error:
|
|
summary: 'Server Error'
|
|
description: 'Internal server error occurred'
|
|
value:
|
|
error: 'Internal Server Error'
|
|
message: 'Something went wrong on our end'
|
|
code: 'INTERNAL_ERROR'
|
|
post:
|
|
summary: 'Create a new user'
|
|
operationId: 'createUser'
|
|
requestBody:
|
|
required: true
|
|
content:
|
|
application/json:
|
|
schema:
|
|
type: object
|
|
required:
|
|
- name
|
|
- email
|
|
properties:
|
|
name:
|
|
type: string
|
|
example: 'John Doe'
|
|
email:
|
|
type: string
|
|
format: email
|
|
example: 'john@example.com'
|
|
examples:
|
|
valid_user:
|
|
summary: 'Valid User'
|
|
description: 'A valid user creation request'
|
|
value:
|
|
name: 'John Doe'
|
|
email: 'john@example.com'
|
|
invalid_user:
|
|
summary: 'Invalid User'
|
|
description: 'An invalid user creation request'
|
|
value:
|
|
name: ''
|
|
email: 'invalid-email'
|
|
responses:
|
|
'201':
|
|
description: 'User created successfully'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
created:
|
|
summary: 'User Created'
|
|
description: 'Successfully created user'
|
|
value:
|
|
id: 123
|
|
name: 'John Doe'
|
|
email: 'john@example.com'
|
|
created_at: '2023-01-01T00:00:00Z'
|
|
'400':
|
|
description: 'Bad Request'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
validation_error:
|
|
summary: 'Validation Error'
|
|
description: 'Invalid user data'
|
|
value:
|
|
error: 'Validation failed'
|
|
message: 'Name and email are required'
|
|
code: 'VALIDATION_ERROR'
|
|
/users/{id}:
|
|
get:
|
|
summary: 'Get user by ID'
|
|
operationId: 'getUserById'
|
|
parameters:
|
|
- name: id
|
|
in: path
|
|
required: true
|
|
schema:
|
|
type: integer
|
|
example: 123
|
|
responses:
|
|
'200':
|
|
description: 'User found'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
found:
|
|
summary: 'User Found'
|
|
description: 'User successfully retrieved'
|
|
value:
|
|
id: 123
|
|
name: 'John Doe'
|
|
email: 'john@example.com'
|
|
created_at: '2023-01-01T00:00:00Z'
|
|
'404':
|
|
description: 'User not found'
|
|
content:
|
|
application/json:
|
|
examples:
|
|
not_found:
|
|
summary: 'User Not Found'
|
|
description: 'User with the specified ID does not exist'
|
|
value:
|
|
error: 'Not Found'
|
|
message: 'User with ID 123 not found'
|
|
code: 'USER_NOT_FOUND'
|