Skip to content

Conversation

@wouterj
Copy link
Member

@wouterj wouterj commented Nov 29, 2025

Some syntax warnings found by the phpDocument parser that were introduced in the past year.

I'll see if I can maybe add a new CI job with the new parser, which is a lot more detailed about syntax mistakes. That'll help us prepare for the migration.

@carsonbot carsonbot added this to the 7.3 milestone Nov 29, 2025
@carsonbot carsonbot changed the title Fix syntax errors/warnings in 6.4 Fix syntax errors/warnings in 6.4 Nov 29, 2025
@wouterj wouterj changed the base branch from 7.3 to 6.4 November 29, 2025 21:35
in the development branch.
* **Bug**: Only for bug fixes; We are very conservative when it comes to
merging older, but still maintained, branches. Read the :doc:`maintenance`
merging older, but still maintained, branches. Read the :doc:`/contributing/code/maintenance`
Copy link
Member Author

@wouterj wouterj Nov 29, 2025

Choose a reason for hiding this comment

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

@OskarStark this might be an interesting one for DOCtor when you have time: we want all doc references to be absolute paths, so the links don't break when moving documents/sections. This has been a rule since forever, but every once in a while one relative path slips in :)

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, I created an issue for DOCtor

@OskarStark
Copy link
Contributor

Thank you @wouterj.

@OskarStark OskarStark merged commit 3f6a403 into symfony:6.4 Nov 29, 2025
3 checks passed
@wouterj wouterj deleted the fix-build-errors-64 branch November 29, 2025 21:38
OskarStark added a commit that referenced this pull request Nov 29, 2025
This PR was merged into the 7.3 branch.

Discussion
----------

 Fix syntax errors/warnings in 7.3

Like #21614, but for things introduced in 7.3.

Commits
-------

882b571 Fix syntax errors/warnings in 7.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants