Skip to content

Conversation

@me-manikanta
Copy link

Description

This change enhances the Bruno language parser to properly handle multiline text blocks (delimited with triple quotes) in multipart form fields that include content type annotations.

Improvements:

  • Update grammar definition to correctly recognize multiline blocks with @ContentType annotations
  • Enhanced multipartExtractContentType function to properly extract content and type annotations
  • Added indentation handling to preserve proper structure while removing common indentation
  • Updated the test cases to address this scenario.

This fixes the multipart form data parsing issue when using multiline text with content type annotations.

Contribution Checklist:

  • The pull request only addresses one issue or adds one feature.
  • The pull request does not introduce any breaking changes
  • I have added screenshots or gifs to help explain the change if applicable.
  • I have read the contribution guidelines.
  • Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

#4457

…ons in .bru files

This change enhances the Bruno language parser to properly handle multiline text blocks
(delimited with triple quotes) in multipart form fields that include content type annotations.

Improvements:
- Update grammar definition to correctly recognize multiline blocks with @ContentType annotations
- Enhanced multipartExtractContentType function to properly extract content and type annotations
- Added indentation handling to preserve proper structure while removing common indentation
- Updated the test cases to address this scenario.

This fixes the multipart form data parsing issue when using multiline text with content type annotations.
@bijin-bruno
Copy link
Collaborator

Hey @me-manikanta

We’ve merged an alternative solution (#6217) that is cleaner, and better aligned with our long-term maintainability goals, so I’ll be closing this one.

Really appreciate the effort you put into this — and I hope to see more contributions from you in the future! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants