Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[TypeInfo] use an EOL-agnostic approach to parse class uses#60909

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
xabbuh wants to merge1 commit intosymfony:7.2
base:7.2
Choose a base branch
Loading
fromxabbuh:issue-60906

Conversation

xabbuh
Copy link
Member

QA
Branch?7.2
Bug fix?yes
New feature?no
Deprecations?no
IssuesFix#60906
LicenseMIT

@carsonbot

This comment was marked as outdated.

@@ -82,6 +83,22 @@ public function testCollectUses()
$this->assertEquals($uses,$this->typeContextFactory->createFromReflection(new \ReflectionParameter([DummyWithUses::class,'setCreatedAt'],'createdAt'))->uses);
}

publicfunctiontestCollectUsesWindowsLineEndings()
{
Copy link
Member

Choose a reason for hiding this comment

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

I suggest adding an assertion that theDummyWithUsesWindowsLineEndings.php file contains\r\n, to avoid having someone changing the line endings (by mistake or intentionally) and making this test useless.
This could happen for instance for contributors on Windows using git's newline conversion features (maybe we could even avoid that specific case with a.gitattributes telling git we want Windows line endings in this specific file)

OskarStark and xabbuh reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I added both the assertion inside the test as well as entries to the relevant.gitattributes files

@xabbuhxabbuhforce-pushed theissue-60906 branch 4 times, most recently frome803276 to76ad82bCompareJune 26, 2025 11:08
@@ -7,5 +7,6 @@
/src/Symfony/Component/Translation/Bridgeexport-ignore
/src/Symfony/Component/Emoji/Resources/data/*linguist-generated=true
/src/Symfony/Component/Intl/Resources/data/*/*linguist-generated=true
/src/Symfony/Component/TypeInfo/Tests/Fixtures/DummyWithUsesWindowsLineEndings.phptexteol=crlf
Copy link
Member

Choose a reason for hiding this comment

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

I don't think we need this ifsrc/Symfony/Component/TypeInfo/.gitattributes already defines it

GromNaN reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Are you sure thatsrc/Symfony/Component/TypeInfo/.gitattributes is evaluated when the mono-repo is checked out?

Copy link
Member

Choose a reason for hiding this comment

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

yes. git respects all.gitattributes files, not just the file at the root of the repo (same for.gitignore files)

GromNaN and xabbuh reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

alright 👍 I reverted this change

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@stofstofstof left review comments

Assignees
No one assigned
Projects
None yet
Milestone
7.4
Development

Successfully merging this pull request may close these issues.

[TypeInfo]TypeContextFactory::collectUses returns values with;
3 participants
@xabbuh@carsonbot@stof

[8]ページ先頭

©2009-2025 Movatter.jp