deprecation-contracts | generic function and convention to trigger deprecation | Web Framework library

by symfony PHP Version: v2.2.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | deprecation-contracts Summary

deprecation-contracts is a PHP library typically used in Server, Web Framework, Symfony applications. deprecation-contracts has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

A generic function and convention to trigger deprecation notices. This package provides a single global function named trigger_deprecation() that triggers silenced deprecation notices. By using a custom PHP error handler such as the one provided by the Symfony ErrorHandler component, the triggered deprecations can be caught and logged for later discovery, both on dev and prod environments. The function requires at least 3 arguments: - the name of the Composer package that is triggering the deprecation - the version of the package that introduced the deprecation - the message of the deprecation - more arguments can be provided: they will be inserted in the message using printf() formatting. This will generate the following message: Since symfony/blockchain 8.9: Using "bitcoin" is deprecated, use "fabcoin" instead. While not necessarily recommended, the deprecation notices can be completely ignored by declaring an empty function trigger_deprecation() {} in your application.

Support

Quality

Security

License

Reuse

Support

deprecation-contracts has a medium active ecosystem.

It has 1728 star(s) with 9 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

deprecation-contracts has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of deprecation-contracts is v2.2.0

Quality

deprecation-contracts has 0 bugs and 0 code smells.

Security

deprecation-contracts has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

deprecation-contracts code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

deprecation-contracts is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

deprecation-contracts releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of deprecation-contracts

Get all kandi verified functions for this library.

deprecation-contracts Key Features

No Key Features are available at this moment for deprecation-contracts.

deprecation-contracts Examples and Code Snippets

No Code Snippets are available at this moment for deprecation-contracts.

Community Discussions

Trending Discussions on deprecation-contracts

Composer post-install scripts not executed

Problem : randomly generate data from a table with a factory

How to prevent Swagger UI from losing authentication upon browser reload

Composer 2.0.8 issue package-versions-deprecated

Laravel 7 Composer install error exception

Laravel installation and create-project issue

QUESTION

Composer post-install scripts not executed

Asked 2022-Jan-21 at 09:47

I am trying to build a docker image with a PHP application in it.

This application installs some dependencies via composer.json and, after composer install, needs some customizations done (eg some files must be copied from vendor folder into other locations and so on).

So I have written these steps as bash commands and putted in the composer.json post-install-cmd section.

This is my composer.json (I've omitted details, but the structure is the same):

...

ANSWER

Answered 2022-Jan-21 at 09:22

Please have a look at the documentation of Composer scripts. It explains pretty obvious:

post-install-cmd: occurs after the install command has been executed with a lock file present.

If you are using composer install with a lock file not present (as indicated from the console output), this event is not fired.

Source https://stackoverflow.com/questions/70788808

QUESTION

Problem : randomly generate data from a table with a factory

Asked 2021-Oct-05 at 15:09

I want take a random id already existing from my garage table, so i have a problem.

...

ANSWER

Answered 2021-Oct-05 at 14:46

The inRandomOrder method may be used to sort the query results randomly. it has no argument, you can use it like:

Source https://stackoverflow.com/questions/69452488

QUESTION

How to prevent Swagger UI from losing authentication upon browser reload

Asked 2021-Mar-20 at 18:29

While my end goal is to prevent Swagger UI from losing authentication upon browser reload, I believe I might have found a solution assuming swagger-ui parameters can be changed when using api-platform, and described it at the tail of this post.

A REST API uses Symfony, API-platform and authenticates using JWT and documentation is provided by swagger-ui. On the swagger-ui page, after submitting the apiKey, future requests include it in the header, however, if the browser is refreshed, the authorization token is lost.

There has been some discussion on this topic primarily on this github post and some on this stackoverflow post, and the general consensus seems to be that swagger-ui there is no "official" way to persist tokens.

Overall Swagger UI does not store tokens, and probably on purpose. There is no switch to enable this, but looks like there are little things that can be done to remember a token via cookie, local storage, indexdb, etc and when the page is reloaded, populate the token back in.

The swagger configuration documentation, however, appears to have an Authorization parameter which will allow the authorization data to be persisted upon browser refresh.

Parameter name: persistAuthorization
Docker variable: PERSIST_AUTHORIZATION
Description: Boolean=false. If set to true, it persists authorization data and it would not be lost on browser close/refresh

Assuming I correctly interpret the Swagger documentation, how can the persistAuthorization parameter be set to true?

When modifying config/api_platform.yaml to set persistAuthorization, I received errors Unrecognized option "persistAuthorization" under "api_platform.swagger.api_keys.apiKey". Available options are "name", "type". and Unrecognized option "persistAuthorization" under "api_platform.swagger". Available options are "api_keys", "versions".

...

ANSWER

Answered 2021-Mar-20 at 17:58

You can for now use the dev version

Source https://stackoverflow.com/questions/66640812

QUESTION

Composer 2.0.8 issue package-versions-deprecated

Asked 2020-Dec-17 at 14:30

Using php 7.2

...

ANSWER

Answered 2020-Dec-17 at 14:30

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

Source https://stackoverflow.com/questions/65149298

QUESTION

Laravel 7 Composer install error exception

Asked 2020-Sep-22 at 14:11

While creating a new laravel project with composer create-project --prefer-dist laravel/laravel:^7.0 projectx an error exception occurred

[ErrorException]
copy(/Users/me/.composer/cache/files/symfony/deprecation-contracts/99b9801994a098b194130905f1f0df2d1f43254c.zip): failed to open stream: Permission denied

I deleted the vendor folder then ran composer install command again but ended up with the same error. This happened after symfony/deprecation-contracts is downloaded as you can see here

I need help me on the reason why this is happening and how to go about fixing it

...

ANSWER

Answered 2020-Sep-22 at 13:46

Give full access of .composer to user.

Source https://stackoverflow.com/questions/64009232

QUESTION

Laravel installation and create-project issue

Asked 2020-Sep-15 at 16:55

I was facing an issue to install laravel in my ubuntu. Please help me.

...

ANSWER

Answered 2020-Sep-15 at 16:55

I used this and It works for me.

Source https://stackoverflow.com/questions/63856646

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install deprecation-contracts

You can download it from GitHub.
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: