Releases: ElementaryFramework/WaterPipe
Releases · ElementaryFramework/WaterPipe
v1.5.0
v1.4.1
v1.4.0
New Features
- Raw, lage file uploads can now be handled with WaterPipe using the RawFileUploadStream class
- Thanks to @manitra, you are now able to catch the runtime exception in your 500 error handler with
Request::getRunningException()
- WaterPipe now has a better system to log errors, and let the ability to customize it, see issue #6 and PR #7 to learn more
Breaking Changes
- The use of
WaterPipeConfig::setUseStderr()
andWaterPipeConfig::useStderr()
are now deprecated. You have to useWaterPipeConfig::setErrorLogger()
to define theIErrorLogger
implementation to use.
v1.3.0
Some improvements are made:
- Ability to initialize HTTP headers through the constructor (2f23912)
- Add support for OPTIONS HTTP header (2b06269)
- Add new ways to use middlewares, with the ability to create self-middlewared Routes (f5ff09a)
- The Request class can now handle raw request body when the content can not be automatically parsed into a RequestData instance (1ea38c9)
Note that this behaviour may change in the future of WaterPipe, and will be configured through
WaterPipeConfig
. - Add quick methods to play with CORS HTTP headers (eaff994)
v1.2.3
List of changes in this release:
- When adding sub pipes, middlewares of parent pipe are propagated (790a1dc)
- The request URI match test is more permissive (e67f3fc)
- When sending requests using the Request class, headers are now removed from the Response body (0f104db)
- Better request body detection (43bc90c)
- Add support to detect headers in servers not based on Apache (601931d)
- Other bug fixes and minor improvements...
v1.2.1
This release comes with minor improvements:
- The
Response
can now be send as parts (see commit9ff8c3b
) HEAD
andPATCH
request methods and handlers are added in routers and pipes (see commitece9c18
)- Introduce a
RouteMap
class used to map an entire URI to a method (see commit6c9e4a0
)
v1.2.0
This release fixes a lot of issues and add new features to WaterPipe:
- Some errors has been fixedin the README
- You can now configure how WaterPipe manage errors through the WaterPipeConfig class. You can choose if errors and exceptions must be thrown normally or must be catched and writed in the stderr PHP stream (see
0ebb45b
) - Now you can create and send your own Request objects through WaterPipe, and get a Response object as result.
- The Router has been optimized and can now parse request with JSON, XML and raw bodies
v1.1.0
This release give some minor updates, and a lot of bug fixes:
- Correct the use of the Location response header
- The Route constructor now take the handled URI
- Allow the use of custom regexes in route URIs (see 294748b)
- The errors registry and the middleware registry is now propagated into plugins and sub-pipes (see 1acea20 and 64573c5)
- Run the 500 error from the registry - if any - on any exceptions thrown
- Clean code and add some doc blocks comments