SDK Binding GA Changes #371
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces support for SDK binding through modelBindingData and collectionModelBindingData parameters in the Azure Functions Node.js library, along with ServiceBus trigger enhancements.
Key Changes
Core RPC Data Conversion Enhancement
Added modelBindingData support: Enhanced fromRpcTypedData to handle individual model binding data objects with automatic client creation through ResourceFactoryResolver
Added collectionModelBindingData support: Added support for collections of model binding data objects, processing the first item in the collection as the source
Error handling: Comprehensive error handling with user-friendly messages when extensions library is not registered
Resource factory integration: Integration with @azure/functions-extensions-base for automatic SDK client creation
ServiceBus Trigger Enhancements
Type flexibility: Updated ServiceBusQueueHandler to accept unknown | any for broader message type compatibility
Auto-complete control: Added autoCompleteMessages option for controlling automatic message completion
SDK binding flag: Added sdkBinding boolean option for enabling SDK-based operations