@absolutejs/ai 0.0.38 → 0.0.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/ai/index.js CHANGED
@@ -3686,7 +3686,8 @@ var FORM_FIELD_TYPES = [
3686
3686
  "number",
3687
3687
  "select",
3688
3688
  "date",
3689
- "checkbox"
3689
+ "checkbox",
3690
+ "password"
3690
3691
  ];
3691
3692
  var CHART_MAX_SERIES = 8;
3692
3693
  var CHART_MAX_POINTS = 24;
@@ -3870,7 +3871,7 @@ var parseFormField = (raw) => {
3870
3871
  field.placeholder = placeholder;
3871
3872
  if (raw.required === true)
3872
3873
  field.required = true;
3873
- const value = cleanString(raw.value, CELL_MAX_CHARS);
3874
+ const value = type === "password" ? null : cleanString(raw.value, CELL_MAX_CHARS);
3874
3875
  if (value)
3875
3876
  field.value = value;
3876
3877
  const options = cleanStringArray(raw.options, FORM_SELECT_MAX_OPTIONS, LABEL_MAX_CHARS);
@@ -4012,7 +4013,7 @@ var statTilesCard = {
4012
4013
  };
4013
4014
  var formCard = {
4014
4015
  ack: "(form rendered inline \u2014 the member fills and submits it, which runs the bound tool with their values. Do NOT re-ask for these values in text; wait for the submission)",
4015
- description: "Render an inline form when you need SEVERAL structured inputs from the member before running a tool (task details, scheduling constraints, outreach parameters) \u2014 one form beats asking field-by-field in prose. Bind submit to one of YOUR tools with any values you already know pre-filled in submit.input; on submit the member's field values are merged into submit.input under each field's name and the tool runs exactly like a clicked action button. Field names must therefore be the tool's actual input property names. Never use it for values you could look up yourself.",
4016
+ description: `Render an inline form when you need SEVERAL structured inputs from the member before running a tool (task details, scheduling constraints, outreach parameters) \u2014 one form beats asking field-by-field in prose. Bind submit to one of YOUR tools with any values you already know pre-filled in submit.input; on submit the member's field values are merged into submit.input under each field's name and the tool runs exactly like a clicked action button. Field names must therefore be the tool's actual input property names. Never use it for values you could look up yourself. Use type "password" for sensitive values (API keys, secrets, credentials) \u2014 the host renders it masked and never pre-fill a value for it.`,
4016
4017
  inputSchema: {
4017
4018
  properties: {
4018
4019
  description: {
@@ -5277,5 +5278,5 @@ export {
5277
5278
  BUILTIN_UI_CARDS
5278
5279
  };
5279
5280
 
5280
- //# debugId=975418BCAB9B044864756E2164756E21
5281
+ //# debugId=F254E5F1D80164DD64756E2164756E21
5281
5282
  //# sourceMappingURL=index.js.map