Skip to content

Recommend including the package name in messages #11522

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 1 commit into from
May 6, 2019

Conversation

greg0ire
Copy link
Contributor

@greg0ire greg0ire commented May 3, 2019

Version numbers, but they make more sense when you know the package
name. Most times, you will be able to figure it out from some FQCN, but
this should make things easier for everyone.

cc @nicolas-grekas who told me about this best practice

I'm unsure about whether this is the best branch for that kind of (pedantic ?) change

Version numbers, but they make more sense when you know the package
name. Most times, you will be able to figure it out from some FQCN, but
this should make things easier for everyone.
@javiereguiluz javiereguiluz added this to the 3.4 milestone May 6, 2019
@javiereguiluz javiereguiluz merged commit d2cfba7 into symfony:3.4 May 6, 2019
javiereguiluz added a commit that referenced this pull request May 6, 2019
This PR was merged into the 3.4 branch.

Discussion
----------

Recommend including the package name in messages

Version numbers, but they make more sense when you know the package
name. Most times, you will be able to figure it out from some FQCN, but
this should make things easier for everyone.

cc @nicolas-grekas who told me about this best practice

I'm unsure about whether this is the best branch for that kind of (pedantic ?) change

Commits
-------

d2cfba7 Recommend including the package name in messages
@javiereguiluz
Copy link
Member

Grégoire, thanks for improving this! While merging I replaced foo-org/bar-lib by vendor-name/package-name because I think it's easier to understand.

@greg0ire greg0ire deleted the deprecation-messages branch May 6, 2019 09:42
@greg0ire
Copy link
Contributor Author

greg0ire commented May 6, 2019

Great, thanks!

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.

5 participants