Summary

Add support for the JSON Schema "readOnly" attribute in node parameter definitions. This enables exposing values for data flow without allowing user configuration, which is essential for internal parameters like branch information.

Business Value

  • Enables cleaner separation between configurable and computed parameters
  • Supports exposing internal state for debugging without risking misconfiguration
  • Follows JSON Schema specification for better interoperability

Features Implemented

  • ReadOnly attribute recognized in parameter schema definitions
  • ReadOnly parameters are displayed but not editable in node type forms
  • Used for "branches" parameter in gateway nodes to show available paths

Comments

joevagyok created an issue. See original summary.

gxleano’s picture

I have contributed (not only by code, but discussion, presentation, testing or anything related).

d34dman’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.