-
Notifications
You must be signed in to change notification settings - Fork 978
fix(ai): Fix logic for merging onDeviceParams #9314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 907badd The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected Products
Test Logs |
expectedInputs: [{ type: 'image' }] | ||
}); | ||
}); | ||
it('sets image as expected input type by default even if other onDeviceParams params are set', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems we should also test the case where expectedInputs are passed in and replace the default expectedInputs
Size Analysis Report 1Affected Products
Test Logs |
User-provided onDeviceParams should do a union merge with default onDeviceParams (default only contains a single value nested 2 levels down - onDeviceParams.createOptions.expectedInputs). In the case that the user explicitly specifies a value for
expectedInputs
, the user's value should override the default.