v1.16.0

Express Gateway v1.16.0 has been released.

This release brings some as bug fixes and an important rewrite of our condition engine that helped us close some important issues as well as implementing a very requested condition: JSON Schema validation!

Added

• A new condition, json-schema, has been added. This will let the gateway validate the payload of your request against a JSON Schema and then decide what to do according to the result. #882

Changed

• A debug log statements gets emitted in case there's no pipeline matching the current request. This will help you diagnose when a 404 is coming from the upstream server or simply from the gateway itself #881
• Package upgrades #880
• Our new contributor @ravikp7 has worked on some inconsistencies between host and hostname used here and there. You'll now get a warning were appropriate as an invite to upgrade your configuration file. #876

Fixed

• A bug in the CLI that would sent incorrect API Key Header to the Admin API has been fixed thanks to @ontehfritz 🚀 #885
• Given my recent full time experience with TypeScript, the types in EG have been updated to better represent what's effectively offered for the plugin API #878
• Fixed the timing on the RateLimit Redis Storage that was incorrectly counting milliseconds instead of seconds. Thanks @ciaranashton for the help #874
• Thanks to an important rewrite we're now able to finally validate the schema for conditions at gateway's loading time and not runtime. This change will finally let you avoid an entire class of bugs before even starting the gateway, instead of getting a crash #882

Express Gateway in production? Let us know!

As always, we're open to any feedback and ready to hear your story of putting Express Gateway in production. In case you're interested, please reach us on Gitter, via email or in any way you want.