Releases: JamesRandall/FunctionMonkey
Output bindings on timer triggers
Now supported. Had overlooked this on the output binding release.
Custom claims binding
A custom claims binder can now be registered to support, for example, claims binding based on external runtime metadata.
OpenAPI route prefix bug fix
- Fixed the issues with API prefixes and the OpenAPI definitions
Routeless HTTP function support
Added support for HTTP triggers with no route in order to support Logic App integrations. To use simply don't use a path on the .HttpRoute and .HttpFunction methods. The function will be given the name of your command.
Output bindings and SignalR support
- Output bindings now supported
- SignalR now supported
- Auto discovery of commands and handlers
- Default connection string support
Minor breaking change to the builder. The .Functions() call has to be the last method that is called so I've made its return type void.
GUIDs supported in route parameters
There is a bug in Azure Functions that prevents GUIDs from working as route parameters - you'll get a bug as the runtime processes your route.
I've added a workaround within Function Monkey so that GUIDs are accepted as strings on the route then internally parse them into GUIDs for binding to commands.
v1.1.1
- Startup structure improvements to support better testing
- Includes v2.0.0 of the test framework with better end to end support for HTTP triggers
Interim Test Framework Update Release v1.1.3
- The acceptance test framework now includes validators in the dispatch pipeline
v1.0.0 - Out of beta release!
- Proxies no longer required
- Validation responses can be customised
- Route parameters can be optional
- Integration test suite
Some easy to fix breaking changes - see migration guide here:
https://functionmonkey.azurefromthetrenches.com/guides/upgradingTo1.0.html