You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(tools): render Ashby object-shaped API errors readably
Ashby documents two error shapes and uses both. The `errors` array form carries
`{ message, parameter }` objects, which stringified to '[object Object]' and hid
the real cause - including the 403 a key gets when it lacks a module permission.
Also adds the shared pieces the new write operations need: one definition of the
custom field value shape for the read and write paths to agree on, and a
normalizer for Ashby's case-sensitive objectType enum so a model emitting
'candidate' fails here with the allowed values rather than at the API.
isPrivate: {type: 'boolean',description: 'Whether the field is private'},
428
+
valueLabel: {
429
+
type: 'json',
430
+
description:
431
+
'Human-readable value label, present only for ValueSelect and MultiValueSelect fields. A string for ValueSelect, an array of strings for MultiValueSelect.',
432
+
optional: true,
433
+
},
434
+
value: {type: 'string',description: 'Raw field value (type depends on fieldType)'},
435
+
}asconstsatisfiesRecord<string,OutputProperty>
436
+
376
437
exportconstCUSTOM_FIELDS_OUTPUT={
377
438
type: 'array',
378
439
description: 'Custom field values',
379
440
items: {
380
441
type: 'object',
381
-
properties: {
382
-
id: {type: 'string',description: 'Custom field UUID'},
0 commit comments