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

[FrameworkBundle] Allow to disable the PropertyAccessor and annotations#17706

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

Closed
GuilhemN wants to merge6 commits intosymfony:masterfromGuilhemN:CONFIG

Conversation

@GuilhemN
Copy link
Contributor

QA
Bug fix?no
New feature?yes
BC breaks?no
Deprecations?no
Tests pass?-
Fixed tickets#13703 (comment)
LicenseMIT

Includes#17690

This PR allows to disableframework.property_access andframework.annotations and deprecate automatically enabling them.

@GuilhemN
Copy link
ContributorAuthor

I'm waiting for feedbacks before fixing all deprecation notices.

->always(function ($v) {
if (!isset($v['property_access'])) {
$v['property_access']['enabled'] =true;
@trigger_error('You must explicitly define wheter to enable "framework.property_access" or not. It will be disabled by default in 4.0',E_USER_DEPRECATED);
Copy link
Member

Choose a reason for hiding this comment

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

not sure if that's a good idea

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

As discussed#13703, it is confusing to have some components enabled by default and some others disabled by default.
BTW this deprecation can be easily fixed in the symfony standard edition.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I commented it for now as there are a lot of changes to make to fix all the deprecations in the core then ...

@fabpot
Copy link
Member

This one should be rebased once#17690 is merged.

@GuilhemNGuilhemNforce-pushed theCONFIG branch 2 times, most recently frome9a2a36 tocbf2211CompareMarch 2, 2016 13:39
@GuilhemN
Copy link
ContributorAuthor

@fabpot I rebased this PR and commented the deprecations notices for now as it make a lot of deprecations to fix...
I'm wondering if this PR should deprecate enablingproperty_access andannotations by default or if we should do that later.

@GuilhemN
Copy link
ContributorAuthor

I removed the deprecations to have something easier to review as we can still add them later.

@GuilhemN
Copy link
ContributorAuthor

I'm closing this for now as the conflicts are too complex to fix.

@GuilhemNGuilhemN deleted the CONFIG branchJune 23, 2016 16:39
fabpot added a commit that referenced this pull requestJun 24, 2016
This PR was merged into the 3.2-dev branch.Discussion----------[FrameworkBundle] Remove redundant code| Q             | A| ------------- | ---| Branch?       | "master"| Bug fix?      | no| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets || License       | MIT| Doc PR        |Was part of#17706.Change the remaining ``isset($config['foo'])`` to ``$this->isConfigEnabled($config['foo'])`` to allow to use parameters to enable a feature.Commits-------a21af88 [FrameworkBundle] Remove redundant code
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@GuilhemN@fabpot@xabbuh@javiereguiluz@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp