AllenNeuralDynamics / AllenNeuralDynamics/prototome-web-ui
Consolidate Mapping of received streams to component and function calls to component
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
This is really two related issues:
#### React component to instrument call (output)
Currently for mapping react component output (buttons, sliders, etc) to instrument functionality, we need to change a specific json string message in each component to match a specific function call on the instrument.
#### instrument (one-liner streams) to react component (input)
For mapping stream names to one-liner functionality, we need to
Stream names and their corresponding functionality is hardcoded.
Specific string names are used across the codebase by various react components to receive instrument input. While these names are called out in **web_ui_config.json**, it's not clear what they correspond to. A one-liner stream needs to be marked with the same stream name and provide the right return type for use by the component.
Example: `prototome_stage_positions` is identified as a data channel in **web_ui_config.json**, and then `prototome_stage_positions` is used in **StagePosVis.tsx**. Elsewhere, a one-liner stream needs to be marked as `prototome_stage_positions` and provide the right return type for the react component to use the information.
#### The Fix
Let's migrate towards having all input/output functionality mapped to a single config file where react components and instrument functionality is outlined in this config.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.