8000 [FrameworkBundle] fix DI extension tests by xabbuh · Pull Request #25847 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[FrameworkBundle] fix DI extension tests #25847

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
Jan 19, 2018
Merged

Conversation

xabbuh
Copy link
Member
@xabbuh xabbuh commented Jan 19, 2018
Q A
Branch? 3.3
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

The failing tests relied on the assets integration being enabled. Since
we never did enable this explicitly, the assets related definitions are
removed now that #25789 was merged which fixed #25760.

The failing tests relied on the assets integration being enabled. Since
we never did enable this explicitly, the assets related definitions are
removed now that symfony#25789 was merged which fixed symfony#25760.
@chalasr
Copy link
Member
chalasr commented Jan 19, 2018

Thank you @xabbuh.

@chalasr chalasr merged commit 1cb8f69 into symfony:3.3 Jan 19, 2018
chalasr added a commit that referenced this pull request Jan 19, 2018
This PR was merged into the 3.3 branch.

Discussion
----------

[FrameworkBundle] fix DI extension tests

| Q             | A
| ------------- | ---
| Branch?       | 3.3
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

The failing tests relied on the assets integration being enabled. Since
we never did enable this explicitly, the assets related definitions are
removed now that #25789 was merged which fixed #25760.

Commits
-------

1cb8f69 [FrameworkBundle] fix DI extension tests
@xabbuh xabbuh deleted the fix-tests branch January 19, 2018 11:18 8000
@@ -1,3 +1,5 @@
framework:
assets:
enabled: true
Copy link
Member Author

Choose a reason for hiding this comment

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

passing null instead of the nested enabled key does not have the desired effect, this seems to be unintentionally broken by the changes made in #25789

xabbuh added a commit to xabbuh/symfony that referenced this pull request Jan 22, 2018
This will revert symfony#25847. Basically, the changes done in symfony#25847 were not
wrong per se. However, those changes were not necessary as the tests
were not failing because of the missing "assets" config, but due to an
issue introduced in the Config component. Furthermore, removing this
part of the config fixtures gives us the benefit that our before
normalization logic that enables assets support when the templating
integration is enabled is properly tested.
fabpot added a commit that referenced this pull request Jan 23, 2018
…(xabbuh)

This PR was merged into the 3.3 branch.

Discussion
----------

[FrameworkBundle] revert useless tests fixtures changes

| Q             | A
| ------------- | ---
| Branch?       | 3.3
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? |no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

This will revert #25847. Basically, the changes done in #25847 were not
wrong per se. However, those changes were not necessary as the tests
were not failing because of the missing "assets" config, but due to an
issue introduced in the Config component. Furthermore, removing this
part of the config fixtures gives us the benefit that our before
normalization logic that enables assets support when the templating
integration is enabled is properly tested.

Commits
-------

fb1be51 revert useless tests fixtures changes
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.

3 participants
0