Skip to content

3.0 changelog #116

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

Merged
merged 3 commits into from
Jun 11, 2025
Merged

3.0 changelog #116

merged 3 commits into from
Jun 11, 2025

Conversation

Crell
Copy link
Collaborator

@Crell Crell commented May 31, 2025

The links point to the live site, like the 2.0 changelog does, so not all of them will work yet. They should once it's tagged and published, though.

Formatting conventions are now provided for compound types (those that include union or intersection type declarations).

* The `|` and `&` symbols and parentheses MUST NOT have leading or trailing spaces.
* If a type declaration is long enough to split to multiple lines, each ANDed block must be on one line, and each ORed block on its own line.

Choose a reason for hiding this comment

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

Suggested change
* If a type declaration is long enough to split to multiple lines, each ANDed block must be on one line, and each ORed block on its own line.
* If a type declaration is long enough to split to multiple lines, each block must be on one line, and each block on its own line.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm not sure this is clear for what it implies. There's 2 different kinds of blocks, so it's not clear what this version is saying.

Choose a reason for hiding this comment

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

Could benefit from an illustrative snippet.

Choose a reason for hiding this comment

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

There may be a misunderstanding on my part with this suggestion.


The original texts says: [...] each ANDed bock must [...] and [...] and each ORed block on [...].

I thought it was a typo, and removing these two words from the text (ANDed & ORed) makes sense.
If it is the case that these words are specific blocks or something, all good 👍

Co-authored-by: Juliette <[email protected]>
Copy link
Contributor

@KorvinSzanto KorvinSzanto left a comment

Choose a reason for hiding this comment

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

Lgtm, nice work 👍🏼

@Crell Crell merged commit 12e50f9 into php-fig:master Jun 11, 2025
@Crell Crell deleted the 3.0-changelog branch June 11, 2025 04:03
@JesusValeraDev
Copy link

Just out of curiosity, is there an ETA for the new 3.0 PER version on the web? :)

@Crell
Copy link
Collaborator Author

Crell commented Jun 23, 2025

When the CC is finished voting: https://groups.google.com/g/php-fig/c/p3TET3uDAgw/m/p9AbDkSRBQAJ

@gharlan
Copy link

gharlan commented Jul 13, 2025

GitHub still shows the 2.0 as latest release because the 3.0 tag does not have release notes:

Bildschirmfoto 2025-07-13 um 16 19 13

@Jean85
Copy link
Member

Jean85 commented Jul 14, 2025

Fixed!

@devfrey
Copy link
Contributor

devfrey commented Jul 14, 2025

Thanks for this release!

The migration guide lists the following under section 4.3:

Class constants must have a visibility and type declared.

However, I'm unable to find anything related to class constant types being required in the spec. Was this an oversight in the spec or in the migration guide?

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.

8 participants