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

[Messenger] rename "envelope items" and move them in the "Stamp" namespace#28911

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

Merged

Conversation

@nicolas-grekas
Copy link
Member

QA
Branch?4.2
Bug fix?no
New feature?no
BC breaks?yes
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

Right now, envelope items are scattered in different sub namespaces and use the "Configuration" suffix.
This makes them hard to discover.
This PR creates a newStamp namespace and moves all "envelope items" there, renaming them to use the "stamp" terminology.

From the changelog:

  • Envelope's constructor andwith method now acceptStampInterface objects as variadic parameters
  • RenamedEnvelopeItemInterface toStampInterface
  • Renamed and movedReceivedMessage,ValidationConfiguration andSerializerConfiguration in theStamp namespace
  • Removed theWrapIntoReceivedMessage (it's untested and unused)

ogizanagi, ro0NL, yceruto, Koc, and dmaicher reacted with thumbs up emoji
Copy link
Contributor

@ogizanagiogizanagi left a comment
edited
Loading

Choose a reason for hiding this comment

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

Copy link
Member

@weaverryanweaverryan left a comment

Choose a reason for hiding this comment

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

I <3 all of this! TheStamp is much more understandable to me than the EnvelopeItems. We are now, for example, "stamping the message validation configuration".

@nicolas-grekasnicolas-grekas merged commit0ad2cb9 intosymfony:masterOct 20, 2018
nicolas-grekas added a commit that referenced this pull requestOct 20, 2018
…he "Stamp" namespace (nicolas-grekas)This PR was merged into the 4.2-dev branch.Discussion----------[Messenger] rename "envelope items" and move them in the "Stamp" namespace| Q             | A| ------------- | ---| Branch?       | 4.2| Bug fix?      | no| New feature?  | no| BC breaks?    | yes| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -Right now, envelope items are scattered in different sub namespaces and use the "Configuration" suffix.This makes them hard to discover.This PR creates a new `Stamp` namespace and moves all "envelope items" there, renaming them to use the "stamp" terminology.From the changelog: * `Envelope`'s constructor and `with` method now accept `StampInterface` objects as variadic parameters * Renamed `EnvelopeItemInterface` to `StampInterface` * Renamed and moved `ReceivedMessage`, `ValidationConfiguration` and `SerializerConfiguration` in the `Stamp` namespace * Removed the `WrapIntoReceivedMessage` (it's untested and unused)Commits-------0ad2cb9 [Messenger] rename "envelope items" and move them in the "Stamp" namespace
@nicolas-grekasnicolas-grekas deleted the messenger-stamps branchOctober 20, 2018 13:06
@sroze
Copy link
Contributor

Oh my god. You hipsters!

ogizanagi reacted with laugh emoji

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

Reviewers

@weaverryanweaverryanweaverryan approved these changes

@chalasrchalasrchalasr approved these changes

@srozesrozeAwaiting requested review from sroze

+1 more reviewer

@ogizanagiogizanagiogizanagi approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

4.2

Development

Successfully merging this pull request may close these issues.

6 participants

@nicolas-grekas@sroze@weaverryan@ogizanagi@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp