Skip to content

[PHPUnitBridge] Fix versionadded notes #7211

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

Closed
wants to merge 3 commits into from
Closed

[PHPUnitBridge] Fix versionadded notes #7211

wants to merge 3 commits into from

Conversation

Jean85
Copy link
Contributor

@Jean85 Jean85 commented Dec 2, 2016

I was reading the docs and noted that those features were marked as present only from Symfony 3.1/2. The reality is that the version that includes that stuff is the bridge's, which is backward compatible!
So, as an example, I can use the bridge v3.2 on my Symfony 2.8 app.

I think it should be helpfull to specify that more clearly.

I was reading the docs and noted that those features were marked as present only from Symfony 3.1/2. The reality is that the version that includes that stuff is the bridge's, which is backward compatible!
So, as an example, I can use the bridge v3.2 on my Symfony 2.8 app.

I think it should be helpfull to specify that more clearly.
Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

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

👍 I like this improvement.

I just have a question: is this change enough to understand that this refers to the component version instead of the Symfony version?

If you agree, maybe we can replace ... in version 3.1. by ... in the 3.1 version of this component. ?

Following javiereguiluz suggestions
@Jean85
Copy link
Contributor Author

Jean85 commented Dec 5, 2016

I completly agree!
I've applied those changes, and I also noticed that I missed one of the other versionadded. Fixed.

Also: should this stuff be backported to the 3.2 branch? Or to an older one?

The ability to disable the deprecation helper was introduced in Symfony
3.1.
The ability to disable the deprecation helper was introduced in the 3.1
version of this component
Copy link
Member

Choose a reason for hiding this comment

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

We should IMO keep the dot at the end of all sentences.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

@xabbuh
Copy link
Member

xabbuh commented Dec 8, 2016

👍

Status: Reviewed

Microfix: restoring punctuation.
@xabbuh
Copy link
Member

xabbuh commented Dec 12, 2016

Thank you @Jean85.

xabbuh added a commit that referenced this pull request Dec 12, 2016
This PR was submitted for the master branch but it was merged into the 3.2 branch instead (closes #7211).

Discussion
----------

[PHPUnitBridge] Fix versionadded notes

I was reading the docs and noted that those features were marked as present only from Symfony 3.1/2. The reality is that the version that includes that stuff is the bridge's, which is backward compatible!
So, as an example, I can use the bridge v3.2 on my Symfony 2.8 app.

I think it should be helpfull to specify that more clearly.

Commits
-------

189b2a5 [PHPUnitBridge] Fix versionadded notes
xabbuh added a commit that referenced this pull request Dec 12, 2016
This PR was submitted for the master branch but it was merged into the 3.1 branch instead (closes #7211).

Discussion
----------

[PHPUnitBridge] Fix versionadded notes

I was reading the docs and noted that those features were marked as present only from Symfony 3.1/2. The reality is that the version that includes that stuff is the bridge's, which is backward compatible!
So, as an example, I can use the bridge v3.2 on my Symfony 2.8 app.

I think it should be helpfull to specify that more clearly.

Commits
-------

59e3f95 [PHPUnitBridge] Fix versionadded notes
@xabbuh xabbuh closed this Dec 12, 2016
xabbuh pushed a commit that referenced this pull request Dec 13, 2016
Due to my own screw-up, I copy pasted the same text in all the changes from my previous PR, #7211, as it's clearly visible from the compare view: https://github.com/symfony/symfony-docs/pull/7211/files

This PR fixes the issue, reverting back the part of text that should be unaffected by my intended changes.
xabbuh added a commit that referenced this pull request Dec 13, 2016
This PR was submitted for the master branch but it was merged into the 3.1 branch instead (closes #7246).

Discussion
----------

[PHPUnitBridge] Fix copy/paste error

Due to my own screw-up, I copy pasted the same text in all the changes from my previous PR, #7211, as it's clearly visible from the compare view: https://github.com/symfony/symfony-docs/pull/7211/files

This PR fixes the issue, reverting back the part of text that should be unaffected by my intended changes.

Commits
-------

97ec0c6 [PHPUnitBridge] Fix copy/paste error
xabbuh pushed a commit that referenced this pull request Dec 13, 2016
Due to my own screw-up, I copy pasted the same text in all the changes from my previous PR, #7211, as it's clearly visible from the compare view: https://github.com/symfony/symfony-docs/pull/7211/files

This PR fixes the issue, reverting back the part of text that should be unaffected by my intended changes.
xabbuh added a commit that referenced this pull request Dec 13, 2016
This PR was submitted for the master branch but it was merged into the 3.2 branch instead (closes #7246).

Discussion
----------

[PHPUnitBridge] Fix copy/paste error

Due to my own screw-up, I copy pasted the same text in all the changes from my previous PR, #7211, as it's clearly visible from the compare view: https://github.com/symfony/symfony-docs/pull/7211/files

This PR fixes the issue, reverting back the part of text that should be unaffected by my intended changes.

Commits
-------

a4241bc [PHPUnitBridge] Fix copy/paste error
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.

4 participants