alyoshenka / alyoshenka/dibiasky

Input for Neopolitan Update operation

Abierto
#63 0 comentarios 0 reacciones 1 asignado Reclamado por @VictorHugoNava Ver en GitHub
priority-medium
Lenguaje dominante
JavaScript
Estrellas
0
Forks
1
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

## (Rough) Spec:
So right now the neopolitan display accepts 3 different types of input to modify its current state: a string message that sets the message that is displaying, a speed value (enum 'slow'/'medium'/'fast') or float that sets how fast the text scrolls, and a boolean value that determine whether the text wraps back around after it finishes displaying or just ends on an empty screen. Right now I'm just passing that data all as strings and then parsing it on the other end, but it would be really neat if the input in the webpage constrained it to the required types. This would involve updating the UpdateOperations component to handle that. I imagine there would be a decent bit of UI work, as well as some state management as well.

### [Reference Page](https://github.com/alyoshenka/dibiasky/blob/main/src/app/operations/HowOperationsWork.md#how-do-the-components-manage-state)

### Current UI:

https://user-images.githubusercontent.com/38815390/236301044-14ca66fa-5a5f-4f46-965a-e94012e0a9bf.mp4

### (Potential) Desired UI:

![Image](https://user-images.githubusercontent.com/38815390/236300967-264228a0-0b0a-488c-be75-68e18e1231d8.png)

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.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.