Skip to content

Conversation

@adaniloff
Copy link

Q A
Branch? 4.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #38482
License MIT
Doc PR

Since the 4.4.15 upgrade, our FOSRest (2.6) configuration did not work anymore.

See the issue in #38482 for more explanation.

Make the test class so it covers the initial behavior on 4.4.14, prior to the 4.4.15 release.
According the the previous commit; in order to keep it consistent with 4.4.14 version.
@adaniloff
Copy link
Author

So I basically reverted 4.4.15 and I kept the test file.
I then constated that there was a test which was failing: testRemovesTwigExceptionListenerIfTwigIsNotUsedAsTemplateEngine which I skipped.

I then add a test in order to cover the 4.4.14 version current behavior.

Obviously, applying the 4.4.15 changes made my test failed.

The question is:

  • is that new behavior from 4.4.15 intended ?
  • if so, then we have an issue because it can breaks backward compatibility in some cases, so I think a patch version is not valid as semantic versionning ?

Curious to know what you guys think about all that.

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

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

/cc @dmolineus for thoughts since @adaniloff apparently disagrees with you.

@adaniloff
Copy link
Author

Closing since it is related to FOSUser.

@adaniloff adaniloff closed this Mar 5, 2021
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