Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Feature request - Prevent local storage of configuration #5638

Closed
efficks opened this issue Dec 11, 2023 · 0 comments
Closed

Feature request - Prevent local storage of configuration #5638

efficks opened this issue Dec 11, 2023 · 0 comments

Comments

@efficks
Copy link

efficks commented Dec 11, 2023

We are using karma in an environment where users have a limited knowledge of the system.
The problem is when we want to change a setting in the configuration file to propagate to all user, the config is not propagated to then because they are saved in the browser local storage.

We need a way to propagate a new config that override the local storage or a way to completely disable the local storage.

Also, maybe karma could use the default and only store in local storage when an actual user change theirs settings. But I also need the feature describe above.

Linked to #5637 and #5479

Repository owner locked and limited conversation to collaborators Mar 31, 2024
@prymitive prymitive converted this issue into discussion #5869 Mar 31, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant