Skip to content
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

feat(core): use a new settings struct to support multiple trackers #113

Merged
merged 16 commits into from
Aug 5, 2024

Conversation

ayuhito
Copy link
Member

@ayuhito ayuhito commented Aug 4, 2024

PR 3/? for #9.

This is a major refactor and improvement on how we approach user settings, allowing for settings to be stored in a JSON blob for the root user since performance isn't critical here.

Ideally, what we will have is a RuntimeConfig that can be dynamically updated and change what type of script is served from /script.js. Since we didn't actually have a framework for properly storing global settings long term, this PR aims to create a good foundation for that.

This will have breaking changes to the API since I went ahead and cleaned up a couple of endpoints such as GET /settings/usage in favour of GET /user/usage. We've also removed the ability to set the resource allocation in the usage menu since it was overly complex, filled with footguns, and an extremely niche use case.

Base automatically changed from tracker/custom to main August 4, 2024 14:41
@ayuhito ayuhito merged commit 83398a9 into main Aug 5, 2024
5 checks passed
@ayuhito ayuhito deleted the feat/settings-json branch August 5, 2024 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant