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

Document allow outdated vendors mode#8686

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

Conversation

@greg0ire
Copy link
Contributor

@weaverryanweaverryan added the Waiting Code MergeDocs for features pending to be merged labelNov 21, 2017
@greg0ire
Copy link
ContributorAuthor

I wonder if should add a table to recommend a usage:

  • strict: recommended for actively maintained projects with few dependencies
  • <some_integer> recommended to transition towards strictness
  • weak_lagging_vendors: recommended in projects when strict cannot be attained
  • weak_vendors: recommended in libraries that struggle to keep up with deprecations
  • weak: not recommended

@greg0iregreg0ire changed the titleDocument weak lagging vendors modeDocument allow outdated vendors modeJan 29, 2018
@greg0ire
Copy link
ContributorAuthor

Here is how the table looks:

screenshot-2018-1-29 the phpunit bridge symfony framework documentation documentation

own dependencies, meaning they do not fix deprecations as soon as
possible, which means there is nothing you can do to fix that (apart
from a pull request on the outdated vendor). This mode allows you to
ignore those deprecations, allowing you to notice when your code is
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe displayyour code bold?

greg0ire reacted with thumbs up emoji
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Or even better,italics.


+------------------------+-----------------------------------------------------+
| Mode| Recommended situation|
+========================+=====================================================+
Copy link
Contributor

Choose a reason for hiding this comment

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

Recommended repeats a lot

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Yeah, not sure what to do about that…

@javiereguiluz
Copy link
Member

@greg0ire the related PR (symfony/symfony#24867) was closed. Could you please tell us if this PR is still relevant or another one is needed to document the changes mentioned in the closed PR? Thanks!

@greg0ire
Copy link
ContributorAuthor

@javiereguiluz this should be closed for now, sorry for leaving it open.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@OskarStarkOskarStarkOskarStark approved these changes

+1 more reviewer

@rzilinrzilinrzilin approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Status: Needs ReviewWaiting Code MergeDocs for features pending to be merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@greg0ire@javiereguiluz@OskarStark@rzilin@weaverryan@xabbuh@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp