-
-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to keep states history or not for any device feature #1599
Conversation
…to Terdious-features-keep-history
Codecov ReportBase: 96.76% // Head: 96.76% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1599 +/- ##
=======================================
Coverage 96.76% 96.76%
=======================================
Files 653 654 +1
Lines 9640 9658 +18
=======================================
+ Hits 9328 9346 +18
Misses 312 312
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Job #464: Bundle Size — 7.01MB (+0.07%).Changed metrics (2/10)
|
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:
npm test
on both front/server)npm run eslint
on both front/server)npm run prettier
on both front/server)npm run compare-translations
on front)front/src/config/demo.js
) so that the demo website is working without a backend? (if needed) See 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
The user is able to tell Gladys if a device feature should keep the state history or not.