fix(frontend): restore Inspection Panel access to hidden advanced fields (1.11.0) (#13626)

fix(frontend): restore Inspection Panel access to hidden advanced fields

Fields that were both advanced=True and listed in HIDDEN_FIELDS became
unreachable from the Inspection Panel: hidden from the node body (advanced)
and removed from the panel (HIDDEN_FIELDS), leaving no edit path. This
affected every HIDDEN_FIELDS entry, originally reported for Chat Input/Output
Store Messages (should_store_message).

Keep HIDDEN_FIELDS out of the default advanced view (the #12473 declutter
intent) but stop filtering them out of edit-fields mode, so users can surface
and edit them via the visibility toggle. Also drop the stale Agent verbose
entry (removed from the component via drop = {verbose}) while keeping the
still-live format_instructions and output_schema hidden. i18n the two
remaining hardcoded panel strings.

Fixes #13595

Author: keval718

src/frontend/src/pages/FlowPage/components/InspectionPanel/__tests__/InspectionPanelFields.hiddenFields.test.tsx

@@ -0,0 +1,134 @@
+import { render, screen } from "@testing-library/react";
+import type { NodeDataType } from "@/types/flow";
+import InspectionPanelFields from "../components/InspectionPanelFields";
+
+// Only the heavy leaf inputs are mocked; the field-filtering logic and the
+// real HIDDEN_FIELDS list run unmocked so this exercises the actual behavior.
+jest.mock("../components/InspectionPanelField", () => {
+  return function MockInspectionPanelField({ name }: { name: string }) {
+    return <div data-testid={`field-${name}`} />;
+  };
+});
+
+jest.mock("../components/InspectionPanelEditField", () => {
+  return function MockInspectionPanelEditField({ name }: { name: string }) {
+    return <div data-testid={`edit-field-${name}`} />;
+  };
+});
+
+// Regression coverage for https://github.com/langflow-ai/langflow/issues/13595
+// A field listed in HIDDEN_FIELDS (ChatInput.should_store_message) must be
+// hidden from the default advanced view yet remain reachable in edit mode, so
+// users keep a path to surface and edit it.
+describe("InspectionPanelFields — HIDDEN_FIELDS reachability (issue #13595)", () => {
+  const createChatInputData = (): NodeDataType =>
+    ({
+      id: "chat-input-1",
+      type: "ChatInput",
+      node: {
+        display_name: "Chat Input",
+        description: "",
+        template: {
+          // Listed in HIDDEN_FIELDS for ChatInput; advanced + shown.
+          should_store_message: {
+            type: "bool",
+            value: true,
+            advanced: true,
+            show: true,
+            display_name: "Store Messages",
+          },
+          // A regular advanced field that is NOT hidden.
+          temperature: {
+            type: "float",
+            value: 0.1,
+            advanced: true,
+            show: true,
+            display_name: "Temperature",
+          },
+        },
+        field_order: [],
+      },
+    }) as unknown as NodeDataType;
+
+  it("hides the field from the default advanced view", () => {
+    render(
+      <InspectionPanelFields
+        data={createChatInputData()}
+        isEditingFields={false}
+      />,
+    );
+
+    expect(
+      screen.queryByTestId("field-should_store_message"),
+    ).not.toBeInTheDocument();
+    // A non-hidden advanced field still renders.
+    expect(screen.getByTestId("field-temperature")).toBeInTheDocument();
+  });
+
+  it("surfaces the field in edit mode so it stays editable", () => {
+    render(
+      <InspectionPanelFields
+        data={createChatInputData()}
+        isEditingFields={true}
+      />,
+    );
+
+    expect(
+      screen.getByTestId("edit-field-should_store_message"),
+    ).toBeInTheDocument();
+    expect(screen.getByTestId("edit-field-temperature")).toBeInTheDocument();
+  });
+
+  // The Agent HIDDEN_FIELDS entry once listed a stale `verbose` field that was
+  // dropped from the component (drop = {"verbose"}); cleaning that up must not
+  // also surface the live format_instructions / output_schema advanced inputs.
+  const createAgentData = (): NodeDataType =>
+    ({
+      id: "agent-1",
+      type: "Agent",
+      node: {
+        display_name: "Agent",
+        description: "",
+        template: {
+          format_instructions: {
+            type: "str",
+            value: "",
+            advanced: true,
+            show: true,
+            display_name: "Output Format Instructions",
+          },
+          output_schema: {
+            type: "table",
+            value: [],
+            advanced: true,
+            show: true,
+            display_name: "Output Schema",
+          },
+        },
+        field_order: [],
+      },
+    }) as unknown as NodeDataType;
+
+  it("keeps Agent format_instructions/output_schema hidden from the default view but editable", () => {
+    const { rerender } = render(
+      <InspectionPanelFields
+        data={createAgentData()}
+        isEditingFields={false}
+      />,
+    );
+
+    expect(
+      screen.queryByTestId("field-format_instructions"),
+    ).not.toBeInTheDocument();
+    expect(screen.queryByTestId("field-output_schema")).not.toBeInTheDocument();
+
+    rerender(
+      <InspectionPanelFields data={createAgentData()} isEditingFields={true} />,
+    );
+
+    expect(
+      screen.getByTestId("edit-field-format_instructions"),
+    ).toBeInTheDocument();
+    expect(screen.getByTestId("edit-field-output_schema")).toBeInTheDocument();
+  });
+});

src/frontend/src/pages/FlowPage/components/InspectionPanel/components/InspectionPanelFields.tsx

@@ -53,7 +53,10 @@ export default function InspectionPanelFields({
       .filter((templateField) => {
         const template = data.node?.template[templateField];
         if (isInternalField(templateField)) return false;
-        if (HIDDEN_FIELDS[data.type]?.includes(templateField)) return false;
+        // HIDDEN_FIELDS are intentionally kept out of the default advanced
+        // view (see advancedFields below) but must remain reachable here in
+        // edit mode so users still have a path to toggle their visibility and
+        // edit them (regression fixed: github.com/langflow-ai/langflow/issues/13595).
         if (INSPECTION_PANEL_ONLY_FIELDS[data.type]?.includes(templateField))
           return false;
         if (

src/frontend/src/pages/FlowPage/components/InspectionPanel/components/hidden-fields.ts

@@ -1,5 +1,8 @@
-// Fields to hide per component type in the InspectionPanel.
-// Add entries here to hide fields without removing backend functionality.
+// Fields hidden from the default InspectionPanel view per component type.
+// These are removed from the streamlined advanced-settings list, but they
+// stay reachable through the panel's edit-fields mode (the visibility toggle),
+// so users still have a path to surface and edit them. Listing a field here
+// must never be the only thing keeping it editable.
 export const HIDDEN_FIELDS: Record<string, string[]> = {
   ChatInput: ["should_store_message", "sender"],
   ChatOutput: ["should_store_message", "sender", "data_template", "clean_data"],
@@ -14,7 +17,10 @@ export const HIDDEN_FIELDS: Record<string, string[]> = {
     "autoset_encoding",
   ],
   UnifiedWebSearch: ["ceid"],
-  Agent: ["verbose"],
+  // `verbose` was dropped from the Agent component's inputs (drop = {"verbose"}),
+  // so it is intentionally absent here; format_instructions and output_schema
+  // are still advanced inputs and stay hidden from the default view.
+  Agent: ["format_instructions", "output_schema"],
   EmbeddingModel: ["show_progress_bar", "chunk_size"],
   Memory: ["sender_type"],
   StructuredOutput: ["system_prompt", "schema_name"],