Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX artifact path validation #3433

Merged
merged 1 commit into from Apr 15, 2024
Merged

Conversation

semul
Copy link
Contributor

@semul semul commented Apr 15, 2024

There Is A Small Problem

Instead Of: public function validateArtifactPath(string $path, string $option)

We Should Use: public function validateArtifactPath(?string $path, string $option)

The PATH might be NULL in some cases.

### There Is A Small Problem

Instead Of: ~~public function validateArtifactPath(string $path, string $option)~~

We Should Use: `public function validateArtifactPath(?string $path, string $option)`

The `PATH` might be `NULL` in some cases.
@bsweeney
Copy link
Member

Apologies, that's a scenario I did not account for. There should be no need to set a path to null, but you are correct that it could happen.

@bsweeney bsweeney merged commit 1722a45 into dompdf:svglib-update Apr 15, 2024
10 checks passed
@bsweeney
Copy link
Member

Apologies, I don't know where my head is right now. I had to re-re-release because the "2.0.x" branch was updated with master in preparation for merging. I reset the branch, the update is in 2.0.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants