create-prisma-php-app 1.0.0

package/vendor/ramsey/uuid/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = .
+BUILDDIR      = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

package/vendor/ramsey/uuid/docs/README.md

@@ -0,0 +1,36 @@
+# ramsey/uuid Documentation
+
+Changes to the documentation are automatically built by [Read the Docs][] and
+viewable from <https://uuid.ramsey.dev>.
+
+## Getting Started
+
+It's probably best to do this in a virtualenv environment, so set one up first:
+
+``` bash
+pip install virtualenvwrapper
+mkvirtualenv ramsey-uuid-docs
+cd docs/
+workon ramsey-uuid-docs
+pip install -r requirements.txt
+```
+
+## Building the Docs
+
+To build the docs, change to the `docs/` directory, and make sure you're working
+on the virtualenv environment created in the last step.
+
+``` bash
+cd docs/
+workon ramsey-uuid-docs
+make html
+```
+
+Then, to view the docs after building them:
+
+``` bash
+open _build/html/index.html
+```
+
+
+[read the docs]: https://readthedocs.org

package/vendor/ramsey/uuid/docs/conf.py

@@ -0,0 +1,103 @@
+# Configuration file for the Sphinx documentation builder.
+#
+# This file only contains a selection of the most common options. For a full
+# list see the documentation:
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
+
+# -- Path setup --------------------------------------------------------------
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+
+import os
+import sphinx_rtd_theme
+import sys
+import datetime
+
+from pygments.lexers.web import PhpLexer
+from sphinx.highlighting import lexers
+from subprocess import Popen, PIPE
+
+def get_version():
+    if os.environ.get('READTHEDOCS') == 'True':
+        return os.environ.get('READTHEDOCS_VERSION')
+
+    pipe = Popen('git branch | grep \*', stdout=PIPE, shell=True, universal_newlines=True)
+    version = pipe.stdout.read()
+
+    if version:
+        return version[2:]
+    else:
+        return 'unknown'
+
+
+# -- Project information -----------------------------------------------------
+
+project = 'ramsey/uuid'
+copyright = '2012-{year}, Ben Ramsey'.format(year = datetime.date.today().strftime('%Y'))
+author = 'Ben Ramsey'
+
+version = get_version().strip()
+release = version
+
+today = datetime.date.today().strftime('%Y-%m-%d')
+
+
+# -- General configuration ---------------------------------------------------
+
+master_doc = 'index'
+highlight_language = 'php'
+
+# enable highlighting for PHP code not between ``<?php ... ?>`` by default
+lexers['php'] = PhpLexer(startinline=True)
+lexers['php-annotations'] = PhpLexer(startinline=True)
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = [
+    'sphinx.ext.autodoc',
+    'sphinx.ext.todo',
+    'sphinxcontrib.phpdomain',
+]
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This pattern also affects html_static_path and html_extra_path.
+exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
+
+pygments_style = 'sphinx'
+
+
+# -- Options for HTML output -------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+#
+html_theme = "sphinx_rtd_theme"
+html_theme_options = {
+    'collapse_navigation': False,
+    'display_version': False
+}
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+html_title = "ramsey/uuid %s Manual" % get_version()
+html_show_sphinx = False
+
+htmlhelp_basename = 'ramsey-uuid-doc'
+
+html_context = {
+    "display_github": True,
+    "github_user": "ramsey",
+    "github_repo": "uuid",
+    "github_version": version,
+    "conf_py_path": "/docs/",
+}

package/vendor/ramsey/uuid/docs/copyright.rst

@@ -0,0 +1,18 @@
+.. _copyright:
+
+=========
+Copyright
+=========
+
+Copyright © 2012-|year| Ben Ramsey <ben@benramsey.com>
+
+ramsey/uuid documentation is licensed under the Creative Commons Attribution 4.0
+International License. To view a copy of this license, visit
+http://creativecommons.org/licenses/by/4.0/ or send a letter to Creative
+Commons, PO Box 1866, Mountain View, CA 94042, USA.
+
+ramsey/uuid source code is licensed under the terms of the MIT License. To view
+a copy of this license, see the LICENSE file distributed with the software or
+visit `<https://opensource.org/licenses/MIT/>`_.
+
+.. |year| date:: %Y

package/vendor/ramsey/uuid/docs/customize/calculators.rst

@@ -0,0 +1,75 @@
+.. _customize.calculators:
+
+=========================
+Using a Custom Calculator
+=========================
+
+By default, ramsey/uuid uses `brick/math`_  as its internal calculator. However,
+you may change the calculator, if your needs require something else.
+
+To swap the default calculator with your custom one, first make an adapter that
+wraps your custom calculator and implements
+:php:interface:`Ramsey\\Uuid\\Math\\CalculatorInterface`. This might look
+something like this:
+
+.. code-block:: php
+    :caption: Create a custom calculator wrapper that implements CalculatorInterface
+    :name: customize.calculators.wrapper-example
+
+    namespace MyProject;
+
+    use Other\OtherCalculator;
+    use Ramsey\Uuid\Math\CalculatorInterface;
+    use Ramsey\Uuid\Type\Integer as IntegerObject;
+    use Ramsey\Uuid\Type\NumberInterface;
+
+    class MyUuidCalculator implements CalculatorInterface
+    {
+        private $internalCalculator;
+
+        public function __construct(OtherCalculator $customCalculator)
+        {
+            $this->internalCalculator = $customCalculator;
+        }
+
+        public function add(NumberInterface $augend, NumberInterface ...$addends): NumberInterface
+        {
+            $value = $augend->toString();
+
+            foreach ($addends as $addend) {
+                $value = $this->internalCalculator->plus($value, $addend->toString());
+            }
+
+            return new IntegerObject($value);
+        }
+
+        /* ... Class truncated for brevity ... */
+
+    }
+
+The easiest way to use your custom calculator wrapper is to instantiate a new
+FeatureSet, set the calculator on it, and pass the FeatureSet into a new
+UuidFactory. Using the factory, you may then generate and work with UUIDs, using
+your custom calculator.
+
+.. code-block:: php
+    :caption: Use your custom calculator wrapper when working with UUIDs
+    :name: customize.calculators.use-wrapper-example
+
+    use MyProject\MyUuidCalculator;
+    use Other\OtherCalculator;
+    use Ramsey\Uuid\FeatureSet;
+    use Ramsey\Uuid\UuidFactory;
+
+    $otherCalculator = new OtherCalculator();
+    $myUuidCalculator = new MyUuidCalculator($otherCalculator);
+
+    $featureSet = new FeatureSet();
+    $featureSet->setCalculator($myUuidCalculator);
+
+    $factory = new UuidFactory($featureSet);
+
+    $uuid = $factory->uuid1();
+
+
+.. _brick/math: https://github.com/brick/math

package/vendor/ramsey/uuid/docs/customize/factory.rst

@@ -0,0 +1,93 @@
+.. _customize.factory:
+
+===========================
+Replace the Default Factory
+===========================
+
+In many of the examples throughout this documentation, we've seen how to
+configure the factory and then use that factory to generate and work with UUIDs.
+
+For example:
+
+.. code-block:: php
+    :caption: Configure the factory and use it to generate a version 1 UUID
+    :name: customize.factory.example
+
+    use Ramsey\Uuid\Codec\OrderedTimeCodec;
+    use Ramsey\Uuid\UuidFactory;
+
+    $factory = new UuidFactory();
+    $codec = new OrderedTimeCodec($factory->getUuidBuilder());
+
+    $factory->setCodec($codec);
+
+    $orderedTimeUuid = $factory->uuid1();
+
+When doing this, the default behavior of ramsey/uuid is left intact. If we call
+``Uuid::uuid1()`` to generate a version 1 UUID after configuring the factory as
+shown above, it won't use :ref:`OrderedTimeCodec <customize.ordered-time-codec>`
+to generate the UUID.
+
+.. code-block:: php
+    :caption: The behavior differs between $factory->uuid1() and Uuid::uuid1()
+    :name: customize.factory.behavior-example
+
+    $orderedTimeUuid = $factory->uuid1();
+
+    printf(
+        "UUID: %s\nBytes: %s\n\n",
+        $orderedTimeUuid->toString(),
+        bin2hex($orderedTimeUuid->getBytes())
+    );
+
+    $uuid = Uuid::uuid1();
+
+    printf(
+        "UUID: %s\nBytes: %s\n\n",
+        $uuid->toString(),
+        bin2hex($uuid->getBytes())
+    );
+
+In this example, we print out details for two different UUIDs. The first was
+generated with the :ref:`OrderedTimeCodec <customize.ordered-time-codec>` using
+``$factory->uuid1()``. The second was generated using ``Uuid::uuid1()``. It
+looks something like this:
+
+.. code-block:: text
+
+    UUID: 2ff06620-6251-11ea-9791-0242ac130003
+    Bytes: 11ea62512ff0662097910242ac130003
+
+    UUID: 2ff09730-6251-11ea-ba64-0242ac130003
+    Bytes: 2ff09730625111eaba640242ac130003
+
+Notice the arrangement of the bytes. The first set of bytes has been rearranged,
+according to the ordered-time codec rules, but the second set of bytes remains
+in the same order as the UUID string.
+
+*Configuring the factory does not change the default behavior.*
+
+If we want to change the default behavior, we must *replace* the factory used
+by the Uuid static methods, and we can do this using the
+:php:meth:`Uuid::setFactory() <Ramsey\\Uuid\\Uuid::setFactory>` static method.
+
+.. code-block:: php
+    :caption: Replace the factory to globally affect Uuid behavior
+    :name: customize.factory.replace-factory-example
+
+    Uuid::setFactory($factory);
+
+    $uuid = Uuid::uuid1();
+
+Now, every time we call :php:meth:`Uuid::uuid() <Ramsey\\Uuid\\Uuid::uuid1>`,
+ramsey/uuid will use the factory configured with the :ref:`OrderedTimeCodec
+<customize.ordered-time-codec>` to generate version 1 UUIDs.
+
+.. warning::
+
+    Calling :php:meth:`Uuid::setFactory() <Ramsey\\Uuid\\Uuid::setFactory>` to
+    replace the factory will change the behavior of Uuid no matter where it is
+    used, so keep this in mind when replacing the factory. If you replace the
+    factory deep inside a method somewhere, any later code that calls a static
+    method on :php:class:`Ramsey\\Uuid\\Uuid` will use the new factory to
+    generate UUIDs.

package/vendor/ramsey/uuid/docs/customize/ordered-time-codec.rst

@@ -0,0 +1,86 @@
+.. _customize.ordered-time-codec:
+
+==================
+Ordered-time Codec
+==================
+
+.. attention::
+
+    :ref:`Version 6, reordered time UUIDs <rfc4122.version6>` are a new version
+    of UUID that eliminate the need for the ordered-time codec. If you aren't
+    currently using the ordered-time codec, and you need time-based, sortable
+    UUIDs, consider using version 6 UUIDs.
+
+UUIDs arrange their bytes according to the standard recommended by `RFC 4122`_.
+Unfortunately, this means the bytes aren't in an arrangement that supports
+sorting by creation time or an otherwise incrementing value. The Percona
+article, "`Storing UUID Values in MySQL`_," explains at length the problems this
+can cause. It also recommends a solution: the *ordered-time UUID*.
+
+RFC 4122 version 1, Gregorian time UUIDs rearrange the bytes of the time fields
+so that the lowest bytes appear first, the middle bytes are next, and the
+highest bytes come last. Logical sorting is not possible with this arrangement.
+
+An ordered-time UUID is a version 1 UUID with the time fields arranged in
+logical order so that the UUIDs can be sorted by creation time. These UUIDs are
+*monotonically increasing*, each one coming after the previously-created one, in
+a proper sort order.
+
+.. code-block:: php
+    :caption: Use the ordered-time codec to generate a version 1 UUID
+    :name: customize.ordered-time-codec-example
+
+    use Ramsey\Uuid\Codec\OrderedTimeCodec;
+    use Ramsey\Uuid\UuidFactory;
+
+    $factory = new UuidFactory();
+    $codec = new OrderedTimeCodec($factory->getUuidBuilder());
+
+    $factory->setCodec($codec);
+
+    $orderedTimeUuid = $factory->uuid1();
+
+    printf(
+        "UUID: %s\nVersion: %d\nDate: %s\nNode: %s\nBytes: %s\n",
+        $orderedTimeUuid->toString(),
+        $orderedTimeUuid->getFields()->getVersion()?->value,
+        $orderedTimeUuid->getDateTime()->format('r'),
+        $orderedTimeUuid->getFields()->getNode()->toString(),
+        bin2hex($orderedTimeUuid->getBytes())
+    );
+
+This will use the ordered-time codec to generate a version 1 UUID and will print
+out details about the UUID similar to these:
+
+.. code-block:: text
+
+    UUID: 593200aa-61ae-11ea-bbf2-0242ac130003
+    Version: 1
+    Date: Mon, 09 Mar 2020 02:33:23 +0000
+    Node: 0242ac130003
+    Bytes: 11ea61ae593200aabbf20242ac130003
+
+.. attention::
+
+    Only the byte representation is rearranged. The string representation
+    follows the format of a standard version 1 UUID. This means only the byte
+    representation of an ordered-time codec encoded UUID may be used for
+    sorting, such as with database results.
+
+    To store the byte representation to a database field, see
+    :ref:`database.bytes`.
+
+.. hint::
+
+    If you use this codec and store the bytes of the UUID to the database, as
+    recommended above, you will need to use this codec to decode the bytes, as
+    well. Otherwise, the UUID string value will be incorrect.
+
+    .. code-block:: php
+
+        // Using a factory configured with the OrderedTimeCodec, as shown above.
+        $orderedTimeUuid = $factory->fromBytes($bytes);
+
+
+.. _RFC 4122: https://tools.ietf.org/html/rfc4122
+.. _Storing UUID Values in MySQL: https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/

package/vendor/ramsey/uuid/docs/customize/timestamp-first-comb-codec.rst

@@ -0,0 +1,72 @@
+.. _customize.timestamp-first-comb-codec:
+
+==========================
+Timestamp-first COMB Codec
+==========================
+
+.. attention::
+
+    :ref:`Version 7, Unix Epoch time UUIDs <rfc4122.version7>` are a new version
+    of UUID that eliminate the need for the timestamp-first COMB codec. If you
+    aren't currently using the timestamp-first COMB codec, and you need
+    time-based, sortable UUIDs, consider using version 7 UUIDs.
+
+:ref:`Version 4, random UUIDs <rfc4122.version4>` are doubly problematic when it
+comes to sorting and storing to databases (see :ref:`database.order`), since
+their values are random, and there is no timestamp associated with them that may
+be rearranged, like with the :ref:`ordered-time codec
+<customize.ordered-time-codec>`. In 2002, Jimmy Nilsson recognized this problem
+with random UUIDs and proposed a solution he called "COMBs" (see "`The Cost of
+GUIDs as Primary Keys`_").
+
+So-called because they *combine* random bytes with a timestamp, the
+timestamp-first COMB codec replaces the first 48 bits of a version 4, random
+UUID with a Unix timestamp and microseconds, creating an identifier that can be
+sorted by creation time. These UUIDs are *monotonically increasing*, each one
+coming after the previously-created one, in a proper sort order.
+
+.. code-block:: php
+    :caption: Use the timestamp-first COMB codec to generate a version 4 UUID
+    :name: customize.timestamp-first-comb-codec-example
+
+    use Ramsey\Uuid\Codec\TimestampFirstCombCodec;
+    use Ramsey\Uuid\Generator\CombGenerator;
+    use Ramsey\Uuid\UuidFactory;
+
+    $factory = new UuidFactory();
+    $codec = new TimestampFirstCombCodec($factory->getUuidBuilder());
+
+    $factory->setCodec($codec);
+
+    $factory->setRandomGenerator(new CombGenerator(
+        $factory->getRandomGenerator(),
+        $factory->getNumberConverter()
+    ));
+
+    $timestampFirstComb = $factory->uuid4();
+
+    printf(
+        "UUID: %s\nVersion: %d\nBytes: %s\n",
+        $timestampFirstComb->toString(),
+        $timestampFirstComb->getFields()->getVersion()?->value,
+        bin2hex($timestampFirstComb->getBytes())
+    );
+
+This will use the timestamp-first COMB codec to generate a version 4 UUID with
+the timestamp replacing the first 48 bits and will print out details about the
+UUID similar to these:
+
+.. code-block:: text
+
+    UUID: 9009ebcc-cd99-4b5f-90cf-9155607d2de9
+    Version: 4
+    Bytes: 9009ebcccd994b5f90cf9155607d2de9
+
+Note that the bytes are in the same order as the string representation. Unlike
+the :ref:`ordered-time codec <customize.ordered-time-codec>`, the
+timestamp-first COMB codec affects both the string representation and the byte
+representation. This means either the string UUID or the bytes may be stored to
+a datastore and sorted. To learn more, see :ref:`database`.
+
+
+.. _The Cost of GUIDs as Primary Keys: https://www.informit.com/articles/printerfriendly/25862

package/vendor/ramsey/uuid/docs/customize/validators.rst

@@ -0,0 +1,39 @@
+.. _customize.validators:
+
+========================
+Using a Custom Validator
+========================
+
+By default, ramsey/uuid validates UUID strings with the lenient validator
+:php:class:`Ramsey\\Uuid\\Validator\\GenericValidator`. This validator ensures
+the string is 36 characters, has the dashes in the correct places, and uses only
+hexadecimal values. It does not ensure the string is of the RFC 4122 variant or
+contains a valid version.
+
+The validator :php:class:`Ramsey\\Uuid\\Rfc4122\\Validator` validates UUID
+strings to ensure they match the RFC 4122 variant and contain a valid version.
+Since it is not enabled by default, you will need to configure ramsey/uuid to
+use it, if you want stricter validation.
+
+.. code-block:: php
+    :caption: Set an alternate validator to use for Uuid::isValid()
+    :name: customize.validators-example
+
+    use Ramsey\Uuid\Rfc4122\Validator as Rfc4122Validator;
+    use Ramsey\Uuid\Uuid;
+    use Ramsey\Uuid\UuidFactory;
+
+    $factory = new UuidFactory();
+    $factory->setValidator(new Rfc4122Validator());
+
+    Uuid::setFactory($factory);
+
+    if (!Uuid::isValid('2bfb5006-087b-9553-5082-e8f39337ad29')) {
+        echo "This UUID is not valid!\n";
+    }
+
+.. tip::
+
+    If you want to use your own validation, create a class that implements
+    :php:interface:`Ramsey\\Uuid\\Validator\\ValidatorInterface` and use the
+    same method to set your validator on the factory.

package/vendor/ramsey/uuid/docs/customize.rst

@@ -0,0 +1,56 @@
+.. _customize:
+
+=============
+Customization
+=============
+
+.. toctree::
+    :titlesonly:
+    :hidden:
+
+    customize/ordered-time-codec
+    customize/timestamp-first-comb-codec
+    customize/calculators
+    customize/validators
+    customize/factory
+
+ramsey/uuid offers a variety of ways to modify the standard behavior of the
+library through dependency injection. Using `FeatureSet`_, `UuidFactory`_, and
+:php:meth:`Uuid::setFactory() <Ramsey\\Uuid\\Uuid::setFactory()>`, you are able
+to replace just about any `builder`_, `codec`_, `converter`_, `generator`_,
+`provider`_, and more.
+
+Ordered-time Codec
+    The ordered-time codec exists to rearrange the bytes of a version 1,
+    Gregorian time UUID so that the timestamp portion of the UUID is
+    monotonically increasing. To learn more, see :ref:`customize.ordered-time-codec`.
+
+Timestamp-first COMB Codec
+    The timestamp-first COMB codec replaces part of a version 4, random UUID
+    with a timestamp, so that the UUID becomes monotonically increasing. To
+    learn more, see :ref:`customize.timestamp-first-comb-codec`.
+
+Using a Custom Calculator
+    It's possible to replace the default calculator ramsey/uuid uses. If your
+    requirements require a different solution for making calculations, see
+    :ref:`customize.calculators`.
+
+Using a Custom Validator
+    If your requirements require a different level of validation or a different
+    UUID format, you may replace the default validator. See
+    :ref:`customize.validators`, to learn more.
+
+Replace the Default Factory
+    Not only are you able to inject alternate builders, codecs, etc. into the
+    factory and use the factory to generate UUIDs, you may also replace the
+    global, static factory used by the static methods on the Uuid class. To find
+    out how, see :ref:`customize.factory`.
+
+
+.. _UuidFactory: https://github.com/ramsey/uuid/blob/5.x/src/UuidFactory.php
+.. _FeatureSet: https://github.com/ramsey/uuid/blob/5.x/src/FeatureSet.php
+.. _codec: https://github.com/ramsey/uuid/tree/5.x/src/Codec
+.. _builder: https://github.com/ramsey/uuid/tree/5.x/src/Builder
+.. _converter: https://github.com/ramsey/uuid/tree/5.x/src/Converter
+.. _provider: https://github.com/ramsey/uuid/tree/5.x/src/Provider
+.. _generator: https://github.com/ramsey/uuid/tree/5.x/src/Generator