Skip to content

Conversation

@samsonasik
Copy link
Member

No description provided.

@samsonasik samsonasik changed the title [Naming] Re-use repetitive DateTimeInterface object type check on services [Naming] Re-use repetitive DateTimeInterface object type check on services into PropertyNaming service May 25, 2025
final class KeepDateTime
{
private ?DateTime $timestamp = null;
private ?\DateTime $timestamp = null;
Copy link
Member Author

Choose a reason for hiding this comment

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

this was invalid fixture, that missing \ suffix as not from use statement, and it inside namespace, so lookup of DateTime under fixture namespace, the extended DateTimeInterface already covered at

$type->isInstanceOf(ClassName::DATE_TIME_INTERFACE)->yes()

@samsonasik
Copy link
Member Author

All checks have passed 🎉 @TomasVotruba I am merging it ;)

@samsonasik samsonasik merged commit 7feb6c8 into main May 25, 2025
45 checks passed
@samsonasik samsonasik deleted the reus branch May 25, 2025 05:35
@github-actions
Copy link
Contributor

This pull request has been automatically locked because it has been closed for 150 days. Please open a new PR if you want to continue the work.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants