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

[Lock] Make SemaphoreStore::isSupported() internal#24057

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

Merged
fabpot merged 1 commit intosymfony:3.4frommaidmaid:lock-3.4
Sep 1, 2017

Conversation

@maidmaid
Copy link
Contributor

@maidmaidmaidmaid commentedAug 31, 2017
edited by xabbuh
Loading

QA
Branch?3.4
Bug fix?no
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets#24053 (comment)
LicenseMIT
Doc PR/

publicstaticfunctionisSupported($blocking =null)
{
if (null !==$blocking) {
@trigger_error(sprintf('The "$blocking" argument of the "%s" is deprecated since 3.4 and will be removed in 4.0.',__METHOD__),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.

Internal call should not trigger deprecation (this argument is used by component console)

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

But how know if call is internal or not?

Copy link
Member

Choose a reason for hiding this comment

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

By passingfalse as second (extra, implicit) argument in each internal call, then triggering only if1 === func_num_args() || func_get_arg(1). But wait,@jderusse do we really need to expose this argument in 3.4? Would it be enough to not add it and consider it exists only for internal calls?

Choose a reason for hiding this comment

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

let's make it final and move on :)

chalasr and jderusse reacted with thumbs up emoji
Copy link
Member

@chalasrchalasrAug 31, 2017
edited
Loading

Choose a reason for hiding this comment

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

@nicolas-grekas doesn't#24053 (comment) still apply when calling the method (no inheritance)?

Choose a reason for hiding this comment

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

nothing will break, so we don't care

Copy link
Member

Choose a reason for hiding this comment

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

ok then :)

Copy link
Member

Choose a reason for hiding this comment

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

I would just mark this method as@internal

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

@internal used.

-----

* added the component
* deprecated the`$blocking` argument of the`SemaphoreStore::isSupported()` method
Copy link
Member

@jderussejderusseAug 31, 2017
edited
Loading

Choose a reason for hiding this comment

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

Thé component is not released yet. Does it make sense to deprecate things here?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

It's usefull to see deprecations linked to 3.4 here I think, else no textual informations is written elsewhere.

Copy link
Member

Choose a reason for hiding this comment

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

Lock was not part of 3.3, so there is nothing to deprecate.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Ok, line removed.

@nicolas-grekasnicolas-grekas added this to the3.4 milestoneAug 31, 2017
@chalasrchalasr changed the title[Lock] Deprecate argument of SemaphoreStore::isSupported()[Lock] Make SemaphoreStore::isSupported() internalSep 1, 2017
@chalasrchalasr added the Lock labelSep 1, 2017
@fabpot
Copy link
Member

Thank you@maidmaid.

@fabpotfabpot merged commit86f2f25 intosymfony:3.4Sep 1, 2017
fabpot added a commit that referenced this pull requestSep 1, 2017
…maid)This PR was merged into the 3.4 branch.Discussion----------[Lock] Make SemaphoreStore::isSupported() internal| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | no| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#24053 (comment)| License       | MIT| Doc PR        | /Commits-------86f2f25 Mark SemaphoreStore::isSupported() as internal
@maidmaidmaidmaid deleted the lock-3.4 branchSeptember 1, 2017 18:30
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas left review comments

@jderussejderussejderusse left review comments

@fabpotfabpotfabpot approved these changes

@javiereguiluzjaviereguiluzjaviereguiluz approved these changes

@xabbuhxabbuhxabbuh approved these changes

@chalasrchalasrchalasr approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

3.4

Development

Successfully merging this pull request may close these issues.

8 participants

@maidmaid@fabpot@javiereguiluz@nicolas-grekas@jderusse@xabbuh@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp