| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
(#784)
|
|
|
|
|
|
name of execute_bash_command inherited from terminal tool) (#869)
|
|
lexicographic sorting (#867)
|
|
|
|
do not have access to README (#866)
|
|
|
|
|
|
`minimatch` (#864)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
command (#854)
|
|
|
|
|
|
|
|
|
|
Submitting without approval to fix broken deployment on main. But also, we should lock this down.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: N. Taylor Mullen <[email protected]>
|
|
|
|
|
|
|
|
|
|
Adds a test case to `settings.test.ts` to specifically verify
the correct resolution of multiple environment variables concatenated
within a single string value (e.g., ${HOST}:${PORT} ).
|
|
Refactors the `resolveEnvVarsInObject` function in settings to
explicitly handle primitive types (null, undefined, boolean, number)
at the beginning of the function. This clarifies the logic for
subsequent string, array, and object processing.
|
