OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	01/06/2025 08:04:38 AM	rwxr-xr-x
📁 .git	-	01/06/2025 08:36:56 AM	rwxr-xr-x
📄 .gitattributes	22 bytes	01/06/2025 08:04:37 AM	rw-r--r--
📁 .github	-	01/06/2025 08:25:46 AM	rwxr-xr-x
📄 .gitignore	37 bytes	01/06/2025 08:04:37 AM	rw-r--r--
📄 CHANGELOG.md	162 bytes	01/06/2025 08:04:37 AM	rw-r--r--
📄 LICENSE	1.06 KB	01/06/2025 08:04:37 AM	rw-r--r--
📄 README.md	1.19 KB	01/06/2025 08:04:38 AM	rw-r--r--
📄 composer.json	876 bytes	01/06/2025 08:04:37 AM	rw-r--r--
📄 function.php	1.02 KB	05/19/2025 10:07:18 AM	rw-r--r--

Editing: README.md

Symfony Deprecation Contracts
=============================

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

Example:
```php
trigger_deprecation('symfony/blockchain', '8.9', 'Using "%s" is deprecated, use "%s" instead.', 'bitcoin', 'fabcoin');
```

This will generate the following message:
`Since symfony/blockchain 8.9: Using "bitcoin" is deprecated, use "fabcoin" instead.`

While not recommended, the deprecation notices can be completely ignored by declaring an empty
`function trigger_deprecation() {}` in your application.