Improvements for tool usage restrictions

Created on 7 May 2025, 8 days ago

Problem/Motivation

Attempting to do the following with tool usage restrictions will result in errors:

  1. Hide an optional property with no value (context error as FixedValue needs a value)
  2. Set a 0 (as the array filter removes it, resulting in the same error as above)
  3. Set values for a list (passes the first value and causes an error on type)

Steps to reproduce

Do any of the above.

Proposed resolution

  1. Only add the constraint if we have a value (but still set as not required)
  2. Make the filter specifically NULL/empty string (as the form would save)
  3. Check the data type and set the entire array if a list
🐛 Bug report
Status

Active

Version

1.1

Component

Code

Created by

🇬🇧United Kingdom andrewbelcher

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024