@averay/codeformat 0.2.7 → 0.2.9

package/vendor/react/cache/src/CacheInterface.php

@@ -1,194 +0,0 @@
-<?php
-
-namespace React\Cache;
-
-use React\Promise\PromiseInterface;
-
-interface CacheInterface
-{
-    /**
-     * Retrieves an item from the cache.
-     *
-     * This method will resolve with the cached value on success or with the
-     * given `$default` value when no item can be found or when an error occurs.
-     * Similarly, an expired cache item (once the time-to-live is expired) is
-     * considered a cache miss.
-     *
-     * ```php
-     * $cache
-     *     ->get('foo')
-     *     ->then('var_dump');
-     * ```
-     *
-     * This example fetches the value of the key `foo` and passes it to the
-     * `var_dump` function. You can use any of the composition provided by
-     * [promises](https://github.com/reactphp/promise).
-     *
-     * @param string $key
-     * @param mixed  $default Default value to return for cache miss or null if not given.
-     * @return PromiseInterface<mixed>
-     */
-    public function get($key, $default = null);
-
-    /**
-     * Stores an item in the cache.
-     *
-     * This method will resolve with `true` on success or `false` when an error
-     * occurs. If the cache implementation has to go over the network to store
-     * it, it may take a while.
-     *
-     * The optional `$ttl` parameter sets the maximum time-to-live in seconds
-     * for this cache item. If this parameter is omitted (or `null`), the item
-     * will stay in the cache for as long as the underlying implementation
-     * supports. Trying to access an expired cache item results in a cache miss,
-     * see also [`get()`](#get).
-     *
-     * ```php
-     * $cache->set('foo', 'bar', 60);
-     * ```
-     *
-     * This example eventually sets the value of the key `foo` to `bar`. If it
-     * already exists, it is overridden.
-     *
-     * This interface does not enforce any particular TTL resolution, so special
-     * care may have to be taken if you rely on very high precision with
-     * millisecond accuracy or below. Cache implementations SHOULD work on a
-     * best effort basis and SHOULD provide at least second accuracy unless
-     * otherwise noted. Many existing cache implementations are known to provide
-     * microsecond or millisecond accuracy, but it's generally not recommended
-     * to rely on this high precision.
-     *
-     * This interface suggests that cache implementations SHOULD use a monotonic
-     * time source if available. Given that a monotonic time source is only
-     * available as of PHP 7.3 by default, cache implementations MAY fall back
-     * to using wall-clock time.
-     * While this does not affect many common use cases, this is an important
-     * distinction for programs that rely on a high time precision or on systems
-     * that are subject to discontinuous time adjustments (time jumps).
-     * This means that if you store a cache item with a TTL of 30s and then
-     * adjust your system time forward by 20s, the cache item SHOULD still
-     * expire in 30s.
-     *
-     * @param string $key
-     * @param mixed  $value
-     * @param ?float $ttl
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function set($key, $value, $ttl = null);
-
-    /**
-     * Deletes an item from the cache.
-     *
-     * This method will resolve with `true` on success or `false` when an error
-     * occurs. When no item for `$key` is found in the cache, it also resolves
-     * to `true`. If the cache implementation has to go over the network to
-     * delete it, it may take a while.
-     *
-     * ```php
-     * $cache->delete('foo');
-     * ```
-     *
-     * This example eventually deletes the key `foo` from the cache. As with
-     * `set()`, this may not happen instantly and a promise is returned to
-     * provide guarantees whether or not the item has been removed from cache.
-     *
-     * @param string $key
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function delete($key);
-
-    /**
-     * Retrieves multiple cache items by their unique keys.
-     *
-     * This method will resolve with an array of cached values on success or with the
-     * given `$default` value when an item can not be found or when an error occurs.
-     * Similarly, an expired cache item (once the time-to-live is expired) is
-     * considered a cache miss.
-     *
-     * ```php
-     * $cache->getMultiple(array('name', 'age'))->then(function (array $values) {
-     *     $name = $values['name'] ?? 'User';
-     *     $age = $values['age'] ?? 'n/a';
-     *
-     *     echo $name . ' is ' . $age . PHP_EOL;
-     * });
-     * ```
-     *
-     * This example fetches the cache items for the `name` and `age` keys and
-     * prints some example output. You can use any of the composition provided
-     * by [promises](https://github.com/reactphp/promise).
-     *
-     * @param string[] $keys A list of keys that can obtained in a single operation.
-     * @param mixed $default Default value to return for keys that do not exist.
-     * @return PromiseInterface<array> Returns a promise which resolves to an `array` of cached values
-     */
-    public function getMultiple(array $keys, $default = null);
-
-    /**
-     * Persists a set of key => value pairs in the cache, with an optional TTL.
-     *
-     * This method will resolve with `true` on success or `false` when an error
-     * occurs. If the cache implementation has to go over the network to store
-     * it, it may take a while.
-     *
-     * The optional `$ttl` parameter sets the maximum time-to-live in seconds
-     * for these cache items. If this parameter is omitted (or `null`), these items
-     * will stay in the cache for as long as the underlying implementation
-     * supports. Trying to access an expired cache items results in a cache miss,
-     * see also [`get()`](#get).
-     *
-     * ```php
-     * $cache->setMultiple(array('foo' => 1, 'bar' => 2), 60);
-     * ```
-     *
-     * This example eventually sets the list of values - the key `foo` to 1 value
-     * and the key `bar` to 2. If some of the keys already exist, they are overridden.
-     *
-     * @param array  $values A list of key => value pairs for a multiple-set operation.
-     * @param ?float $ttl    Optional. The TTL value of this item.
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function setMultiple(array $values, $ttl = null);
-
-    /**
-     * Deletes multiple cache items in a single operation.
-     *
-     * @param string[] $keys A list of string-based keys to be deleted.
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function deleteMultiple(array $keys);
-
-    /**
-     * Wipes clean the entire cache.
-     *
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function clear();
-
-    /**
-     * Determines whether an item is present in the cache.
-     *
-     * This method will resolve with `true` on success or `false` when no item can be found
-     * or when an error occurs. Similarly, an expired cache item (once the time-to-live
-     * is expired) is considered a cache miss.
-     *
-     * ```php
-     * $cache
-     *     ->has('foo')
-     *     ->then('var_dump');
-     * ```
-     *
-     * This example checks if the value of the key `foo` is set in the cache and passes
-     * the result to the `var_dump` function. You can use any of the composition provided by
-     * [promises](https://github.com/reactphp/promise).
-     *
-     * NOTE: It is recommended that has() is only to be used for cache warming type purposes
-     * and not to be used within your live applications operations for get/set, as this method
-     * is subject to a race condition where your has() will return true and immediately after,
-     * another script can remove it making the state of your app out of date.
-     *
-     * @param string $key The cache item key.
-     * @return PromiseInterface<bool> Returns a promise which resolves to `true` on success or `false` on error
-     */
-    public function has($key);
-}

package/vendor/react/child-process/CHANGELOG.md

@@ -1,176 +0,0 @@
-# Changelog
-
-## 0.6.6 (2025-01-01)
-
-This is a compatibility release that contains backported features from the `0.7.x` branch.
-Once v0.7 is released, it will be the way forward for this project.
-
-*   Feature: Improve PHP 8.4+ support by avoiding implicitly nullable types.
-    (#114 by @clue)
-
-*   Improve test suite to run tests on latest PHP versions and report failed assertions.
-    (#113 by @clue)
-
-## 0.6.5 (2022-09-16)
-
-*   Feature: Full support for PHP 8.1 and PHP 8.2 release.
-    (#91 by @SimonFrings and #99 by @WyriHaximus)
-
-*   Feature / Fix: Improve error reporting when custom error handler is used.
-    (#94 by @clue)
-
-*   Minor documentation improvements.
-    (#92 by @SimonFrings and #95 by @nhedger)
-
-*   Improve test suite, skip failing tests on bugged versions and fix legacy HHVM build.
-    (#96 and #98 by @clue and #93 by @SimonFrings)
-
-## 0.6.4 (2021-10-12)
-
-*   Feature / Fix: Skip sigchild check if `phpinfo()` has been disabled.
-    (#89 by @clue)
-
-*   Fix: Fix detecting closed socket pipes on PHP 8.
-    (#90 by @clue)
-
-## 0.6.3 (2021-07-11)
-
-A major new feature release, see [**release announcement**](https://clue.engineering/2021/announcing-reactphp-default-loop).
-
-*   Feature: Simplify usage by supporting new [default loop](https://reactphp.org/event-loop/#loop).
-    (#87 by @clue)
-
-    ```php
-    // old (still supported)
-    $process = new React\ChildProcess\Process($command);
-    $process->start($loop);
-
-    // new (using default loop)
-    $process = new React\ChildProcess\Process($command);
-    $process->start();
-    ```
-
-## 0.6.2 (2021-02-05)
-
-*   Feature: Support PHP 8 and add non-blocking I/O support on Windows with PHP 8.
-    (#85 by @clue)
-
-*   Minor documentation improvements.
-    (#78 by @WyriHaximus and #80 by @gdejong)
-
-*   Improve test suite and add `.gitattributes` to exclude dev files from exports.
-    Run tests on PHPUnit 9, switch to GitHub actions and clean up test suite.
-    (#75 by @reedy, #81 by @gdejong, #82 by @SimonFrings and #84 by @clue)
-
-## 0.6.1 (2019-02-15)
-
-*   Feature / Fix: Improve error reporting when spawning child process fails.
-    (#73 by @clue)
-
-## 0.6.0 (2019-01-14)
-
-A major feature release with some minor API improvements!
-This project now has limited Windows support and supports passing custom pipes
-and file descriptors to the child process.
-
-This update involves a few minor BC breaks. We've tried hard to avoid BC breaks
-where possible and minimize impact otherwise. We expect that most consumers of
-this package will actually not be affected by any BC breaks, see below for more
-details.
-
-*   Feature / BC break: Support passing custom pipes and file descriptors to child process,
-    expose all standard I/O pipes in an array and remove unused Windows-only options.
-    (#62, #64 and #65 by @clue)
-
-    > BC note: The optional `$options` parameter in the `Process` constructor
-      has been removed and a new `$fds` parameter has been added instead. The
-      previous `$options` parameter was Windows-only, available options were not
-      documented or referenced anywhere else in this library, so its actual
-      impact is expected to be relatively small. See the documentation and the
-      following changelog entry if you're looking for Windows support.
-
-*   Feature: Support spawning child process on Windows without process I/O pipes.
-    (#67 by @clue)
-
-*   Feature / BC break: Improve sigchild compatibility and support explicit configuration.
-    (#63 by @clue)
-
-    ```php
-    // advanced: not recommended by default
-    Process::setSigchildEnabled(true);
-    ```
-
-    > BC note: The old public sigchild methods have been removed, but its
-      practical impact is believed to be relatively small due to the automatic detection.
-
-*   Improve performance by prefixing all global functions calls with \ to skip
-    the look up and resolve process and go straight to the global function.
-    (#68 by @WyriHaximus)
-
-*   Minor documentation improvements and docblock updates.
-    (#59 by @iamluc and #69 by @CharlotteDunois)
-
-*   Improve test suite to test against PHP7.2 and PHP 7.3, improve HHVM compatibility,
-    add forward compatibility with PHPUnit 7 and run tests on Windows via Travis CI.
-    (#66 and #71 by @clue)
-
-## 0.5.2 (2018-01-18)
-
-*   Feature: Detect "exit" immediately if last process pipe is closed
-    (#58 by @clue)
-
-    This introduces a simple check to see if the program is already known to be
-    closed when the last process pipe is closed instead of relying on a periodic
-    timer. This simple change improves "exit" detection significantly for most
-    programs and does not cause a noticeable penalty for more advanced use cases.
-
-*   Fix forward compatibility with upcoming EventLoop releases
-    (#56 by @clue)
-
-## 0.5.1 (2017-12-22)
-
-*   Fix: Update Stream dependency to work around SEGFAULT in legacy PHP < 5.4.28
-    and PHP < 5.5.12
-    (#50 and #52 by @clue)
-
-*   Improve test suite by simplifying test bootstrapping logic via Composer and
-    adding forward compatibility with PHPUnit 6
-    (#53, #54 and #55 by @clue)
-
-## 0.5.0 (2017-08-15)
-
-* Forward compatibility: react/event-loop 1.0 and 0.5, react/stream 0.7.2 and 1.0, and Événement 3.0
-  (#38 and #44 by @WyriHaximus, and #46 by @clue)
-* Windows compatibility: Documentate that windows isn't supported in 0.5 unless used from within WSL
-  (#41 and #47 by @WyriHaximus)
-* Documentation: Termination examples
-  (#42 by @clue)
-* BC: Throw LogicException in Process instanciating when on Windows or when proc_open is missing (was `RuntimeException`)
-  (#49 by @mdrost)
-
-## 0.4.3 (2017-03-14)
-
-* Ease getting started by improving documentation and adding examples
-  (#33 and #34 by @clue)
-
-* First class support for PHP 5.3 through PHP 7.1 and HHVM
-  (#29 by @clue and #32 by @WyriHaximus)
-
-## 0.4.2 (2017-03-10)
-
-* Feature: Forward compatibility with Stream v0.5
-  (#26 by @clue)
-
-* Improve test suite by removing AppVeyor and adding PHPUnit to `require-dev`
-  (#27 and #28 by @clue)
-
-## 0.4.1 (2016-08-01)
-
-* Standalone component
-* Test against PHP 7 and HHVM, report test coverage, AppVeyor tests
-* Wait for stdout and stderr to close before watching for process exit
-  (#18 by @mbonneau)
-
-## 0.4.0 (2014-02-02)
-
-* Feature: Added ChildProcess to run async child processes within the event loop (@jmikola)

package/vendor/react/child-process/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2012 Christian Lück, Cees-Jan Kiewiet, Jan Sorgalla, Chris Boden, Igor Wiedler
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is furnished
-to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.