Protocol::Content
Provides transport-independent parsing for media-typed content.
Usage
Please see the project documentation for more details.
- Getting Started - This guide explains how to parse media-typed content using built-in and custom parsers.
Releases
Please see the project releases for all releases.
v0.1.0
- Add media-type parser dispatch for readable content.
- Add JSON, URL-encoded form, and multipart form parsers with explicit convenient defaults.
- Bound JSON input size and nesting depth using consistently named limits.
- Add
ContentTooLargeErrorfor content parser limit violations. - Forward blocks to content handlers for incremental and streaming parsing.
Contributing
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature.'). - Push to the branch (
git push origin my-new-feature). - Create a new pull request.
Running Tests
To run the test suite:
bundle exec susMaking Releases
To make a new release:
bundle exec bake gem:release:patch # or minor or majorDeveloper Certificate of Origin
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
Community Guidelines
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.
See Also
- protocol-http provides HTTP message abstractions.
- protocol-media provides media type abstractions.
- async-rest provides asynchronous REST client abstractions.