generated from nhcarrigan/template
2c64ef089e4c58f64bfa8e8984bfaa65e686f335
CRITICAL BUG: The config store had a race condition in all methods that accessed the current config. The pattern: ```typescript let currentConfig = defaultConfig; config.subscribe((c) => (currentConfig = c))(); ``` This immediately unsubscribes (the `()` at the end), creating a race where sometimes it would get the value, sometimes it wouldn't. This caused: - Config appearing "lost" after permission approvals - Settings resetting to defaults randomly - Model selection not persisting FIX: - Created a proper `getCurrentConfig()` helper that unsubscribes cleanly - Replaced ALL instances of the buggy pattern (12 occurrences!) - getConfig(), updateConfig(), toggles, theme setters, font methods, etc. This should completely fix the config loss issue.
hikari-desktop
Desktop companion application featuring Hikari.
Live Version
This page is currently deployed. View the live website.
Feedback and Bugs
If you have feedback or a bug report, please log a ticket on our forum.
Contributing
If you would like to contribute to the project, you may create a Pull Request containing your proposed changes and we will review it as soon as we are able! Please review our contributing guidelines first.
Code of Conduct
Before interacting with our community, please read our Code of Conduct.
License
This software is licensed under our global software license.
Copyright held by Naomi Carrigan.
Contact
We may be contacted through our Chat Server or via email at contact@nhcarrigan.com
Description