-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Iteration Athens
-
Not Needed
{config.set()}
allows the user to save any key-value pair to config.json. While this might be convenient for storing arbitrary information that is remembered across sessions, it has the side effect of letting the user overwrite some properties that are important for mongosh to function properly, e.g. userId.
We should either have a list of allowed properties and only let the user set those or a list of disallowed properties and let the user set anything but those. I'd lean towards the former, to avoid `config.json` to become too big if users put random stuff into config and ends up slowing down the shell when it starts but I'd be also open to consider the latter.