¡Error 404 me parece bien!
¡Está en progreso!!
El rendimiento es completamente diferente con DuckDB:
1 hora = 184 estados
paso a 24h = 1560 estados
paso a 7 días = 3700 estados
paso a 3 meses = 37300 estados (bueno, pero luego la navegación en este punto) y si hay varios dispositivos, es complicado.
Propongo:
24h y menos sin límite de puntos
Más allá: 4000 puntos / número de características a mostrar
Al hacer zoom, se recalcula para ser cada vez más preciso
Un menú desplegable de selección para mostrar por agregado (como en Metabase)
¡No es una fatalidad!
Terdious:
24h y menos sin límite de puntos
Más allá: 4000 puntos / número de características a mostrar
¿Por qué no poner un límite en todas partes? 4000 puntos me parece exagerado, actualmente en el panel de control mostramos 200
¡Sí! pero siempre con el mismo límite
En realidad, solo hay que mantener exactamente la misma consulta que en el panel de control, pero pidiendo más puntos, y teniendo la posibilidad de especificar un período y no solo una duración
¡Sí, definitivamente!
Perfecto
Vale, veo cómo queda con 1000 puntos.
pierre-gilles:
¡No es una fatalidad!
Vale, lo veremos más tarde entonces ^^
guim31:
Sí, lo había entendido, pero soy impaciente de todos modos. De hecho, creo que la parte de visualización de gráficos necesitaba principalmente la posibilidad de mostrarlos más grandes, ¡y esto es lo mejor para mí!
Entre esto y los sensores binarios, estoy encantado con estos últimos desarrolladores.
¡PR para elegir el número de columnas en el panel de prueba de Gladys Plus en https://terdious-add-choice-number-col.pages.dev/ para los interesados. ^^
Y finalmente la vista extendida de los gráficos:https://terdious-add-expand-charts.pages.dev/
Hola @Terdious y gracias por todas tus PR
Hoy he hecho una serie de revisiones:
He fusionado tu PR sobre el número de columnas dinámicas en el panel de control:
master ← Terdious:add-choice-number-columns-dashboard
ouvert 08:32PM - 03 Jun 24 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- ~~If your changes affects code, did your write the tests?~~
- ~~Are tests passing? (`npm test` on both front/server)~~
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([french forum](https://community.gladysassistant.com/)/[english forum](https://en-community.gladysassistant.com/)) for testing before merging.
- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Adding the deletion or addition of columns to the dashboard
Un pequeño comentario sobre tu PR que ajusta el tamaño de los gráficos:
master ← Terdious:improvement-height-charts
ouvert 01:57PM - 05 Sep 24 UTC
…d on additional features
### Pull Request check-list
To ensure your Pull … Request can be accepted as fast as possible, make sure to review and check all of these items:
- ~~If your changes affects code, did your write the tests?~~
- ~~Are tests passing? (`npm test` on both front/server)~~
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- ~~If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)~~
- ~~Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([french forum](https://community.gladysassistant.com/)/[english forum](https://en-community.gladysassistant.com/)) for testing before merging.~~
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- ~~If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).~~
- ~~Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).~~
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Small PR to increase the height of the charts depending on the number of features selected. Currently the curve is squashed to make room for the legend and contain the size of the box.
Para la PR sobre los dispositivos binarios, tengo algunos comentarios, pero nada serio.
master ← Terdious:add-binary-chart
ouvert 11:44AM - 03 Jun 24 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [x] If your changes affects code, did your write the tests?
- [x] Are tests passing? (`npm test` on both front)
- [x] Is the linter passing? (`npm run eslint` on both front)
- [x] Did you run prettier? (`npm run prettier` on both front)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([french forum](https://community.gladysassistant.com/)/[english forum](https://en-community.gladysassistant.com/)) for testing before merging.
- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Taken from the original PR: #Binary graph #1948
Thanks to @callemand for all the work done
Gracias de nuevo por estas PRs que claramente van a gustar a mucha gente, ¡yo el primero!
No dudes en preguntar si tienes alguna pregunta sobre los comentarios
Hola @pierre-gilles , ninguna pregunta, gracias por las revisiones.
¡Muchas gracias por vuestro trabajo, señores ^^
@Terdious Gracias por tus comentarios
¡He fusionado la PR sobre los gráficos binarios! Para la otra PR, hay un conflicto con los gráficos binarios porque afecta a lo mismo. ¿Podrías corregir el conflicto?
Edición: Construcción en curso de Gladys Assistant 4.46.0. ¡Salida en 4h!
https://github.com/GladysAssistant/Gladys/actions/runs/11208245077
¡Genial!
Conflicto corregido y probado.
! En construcción (no completamente funcional y diseño no definitivo). Permite hacerse una idea del desarrollo en curso. Lo he puesto en construcción automática, por lo que se actualizará a medida que avance.
