Previously, the bash escaping functions (`escapeBashEnvValue()` and `escapeBashDoubleQuoted()`) had strict string type hints that rejected null values, causing deployment failures when environment variables had null values. Changes: - Updated both functions to accept nullable strings (`?string $value`) - Handle null/empty values by returning empty quoted strings (`''` for single quotes, `""` for double quotes) - Added 3 new tests to cover null and empty value handling - All 29 tests pass This fix ensures deployments work correctly even when environment variables have null values, while maintaining the existing behavior for all other cases. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api.php | ||
| applications.php | ||
| constants.php | ||
| databases.php | ||
| docker.php | ||
| domains.php | ||
| github.php | ||
| notifications.php | ||
| parsers.php | ||
| proxy.php | ||
| remoteProcess.php | ||
| services.php | ||
| shared.php | ||
| socialite.php | ||
| subscriptions.php | ||
| sudo.php | ||
| timezone.php | ||