Skip to content

Conversation

@Girgias
Copy link
Member

@Girgias Girgias commented Nov 4, 2025

Follow-up from #4936 as I have various manual style guide and markup complaints with the new (and existing) docs.

@AllenJB please review as the original author. :)

Comment on lines 631 to 632
This is usually know if when examining the return code from the method
that raised the error condition anyway.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is usually known by examining the return code from the method
that raised the error condition anyway.

@AllenJB
Copy link
Contributor

AllenJB commented Nov 4, 2025

@Girgias One minor issue. Other than that looks fine to me. 👍

I'll keep these in mind as I make future contributions.

Copy link
Member

@kamil-tekiela kamil-tekiela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from that one thing AllenJB mentioned, it looks good. I even prefer it that this is done as a separate PR because it's easier to review.

@Girgias Girgias force-pushed the pdo-fetch-follow-up branch from 2e7afe6 to 2ff5759 Compare November 10, 2025 03:18
@Girgias Girgias merged commit 7e384b2 into php:master Nov 10, 2025
2 checks passed
@Girgias Girgias deleted the pdo-fetch-follow-up branch November 10, 2025 03:24
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.

3 participants