Context
From GF++ Alignment sync meeting (2026-04-09).
Problem
Component properties like "bend type" are currently plain text fields. Ideally, when a property expects a component reference (e.g., a bend), the editor should offer a filtered selector showing only relevant models from the PDK instead of requiring the user to type a name.
Goal
Make the property editor aware of property types so it can offer appropriate input widgets (e.g., a model selector filtered by tag). The main open question is where to get the type information from — this needs research into gdsfactory's type annotations and how to propagate them to the editor.
Meeting Discussion
- Joaquin: Can you choose bend type from a selector? Currently just a text field with no PDK awareness
- Alejandro: Components should have tags (e.g., "bends") so the selector can filter to relevant models
- Sebastian: Advanced type annotations would be needed, but Python annotations are not fully standardized
- Pepijn: If type annotation info is propagated from Python, the existing model selector could be filtered
Context
From GF++ Alignment sync meeting (2026-04-09).
Problem
Component properties like "bend type" are currently plain text fields. Ideally, when a property expects a component reference (e.g., a bend), the editor should offer a filtered selector showing only relevant models from the PDK instead of requiring the user to type a name.
Goal
Make the property editor aware of property types so it can offer appropriate input widgets (e.g., a model selector filtered by tag). The main open question is where to get the type information from — this needs research into gdsfactory's type annotations and how to propagate them to the editor.
Meeting Discussion