[OPIK-4211] [SDK] Fix config file path expansion to support ~/.opik.config #5044
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…onfig Add expandPath function to handle tilde expansion in OPIK_CONFIG_PATH environment variable. The default config path now uses path.join for absolute path resolution, and custom paths with tilde are properly expanded using regex pattern matching. Implements OPIK-4211: [TS SDK] Default ~/.opik.config config path is not used
awkoy
pushed a commit
that referenced
this pull request
Feb 5, 2026
…onfig (#5044) Add expandPath function to handle tilde expansion in OPIK_CONFIG_PATH environment variable. The default config path now uses path.join for absolute path resolution, and custom paths with tilde are properly expanded using regex pattern matching. Implements OPIK-4211: [TS SDK] Default ~/.opik.config config path is not used
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
Fixed TypeScript SDK config file path expansion to properly handle tilde (
~) in paths. The issue was that Node.js'sfsmodule doesn't natively expand tilde paths, so~/.opik.configwasn't being found.Implementation:
"~/.opik.config"topath.join(os.homedir(), ".opik.config")for direct absolute path resolutionexpandPath()function using regex pattern/^~(?=$|\/|\\)/to handle tilde expansion inOPIK_CONFIG_PATHenvironment variablefs.existsSync,fs.readFileSync)The regex pattern ensures we only expand
~at the start of the path when followed by end of string, forward slash, or backslash (cross-platform support).Change checklist
Issues
Testing
Added unit test
should expand tilde in OPIK_CONFIG_PATHthat verifies:To test manually:
OPIK_CONFIG_PATH=~/.opik.config(or any path starting with~)Documentation
N/A - No documentation changes required. This is a bug fix that maintains backward compatibility.