Closed fanyipin closed 2 months ago
@xai FYI
@JonasHelming, please assign this issue to me (cannot self-assign). Thanks!
I understand that there should be a priority order where:
1. User-defined settings take precedence, 2. Followed by application-specific settings if defined, 3. Lastly, defaulting to the standard THEIA directory if neither is provided.
Thank you very much @fanyipin for raising this issue!
My understanding here is the same, so I opened PR #13708, which ensures the 1. property, that is currently violated.
Bug Description:
Prior to version 1.44, the ConfigDirUri variable could be customized via process.env.THEIA_CONFIG_DIR. This meant users could set process.env.THEIA_CONFIG_DIR within their application to specify a custom data directory. However, after the introduction of the logic in the app directory in version 1.44, process.env.THEIA_CONFIG_DIR is being re-assigned, which seems to override previous settings. I understand that there should be a priority order where:
Here is the logical code for handling ConfigDirUri, which I understand should not be specified directly if process.env.THEIA_CONFIG_DIR has a value
Steps to Reproduce:
if process.env.THEIA_CONFIG_DIR is specified as a directory, the latest cache file address is not matched
Additional Information