Try Actions

.gitattributes

@@ -0,0 +1,9 @@
+/tests export-ignore
+/phpcs.xml.dist export-ignore
+/phpunit.xml.dist export-ignore
+/.gitattributes export-ignore
+/.github export-ignore
+/.gitignore export-ignore
+/.scrutinizer.yml export-ignore
+/.travis export-ignore
+/.travis.yml export-ignore

.github/FUNDING.yml

@@ -1,5 +1,5 @@
-#github: [goetas,schmittjoh]
-patreon: goetas
+github: [goetas]
+#patreon: goetas
 #open_collective: jms-serializer
 #ko_fi: # Replace with a single Ko-fi username
 #tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel

.github/workflows/ci.yaml

@@ -0,0 +1,59 @@
+# yamllint disable rule:line-length
+# yamllint disable rule:braces
+
+name: Continuous Integration
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  tests:
+    runs-on: ${{ matrix.operating-system }}
+
+    strategy:
+      matrix:
+        operating-system: [ubuntu-latest]
+        php-version: [7.2, 7.3, 7.4]
+        dependencies: ['']
+        include:
+          - { operating-system: 'ubuntu-latest', php-version: '8.0', dependencies: '--ignore-platform-req=php' }
+
+    name: CI on ${{ matrix.operating-system }} with PHP ${{ matrix.php-version }} ${{ matrix.dependencies }}
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Setup PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: ${{ matrix.php-version }}
+          tools: composer:v2
+          extensions: pdo_sqlite
+
+      - name: Get composer cache directory
+        id: composer-cache
+        run: echo "::set-output name=dir::$(composer config cache-files-dir)"
+
+      - name: Cache dependencies
+        uses: actions/cache@v2
+        with:
+          path: ${{ steps.composer-cache.outputs.dir }}
+          key: composer-${{ runner.os }}-${{ matrix.php-version }}-${{ hashFiles('composer.*') }}-${{ matrix.dependencies }}
+          restore-keys: |
+            composer-${{ runner.os }}-${{ matrix.php-version }}-${{ hashFiles('composer.*') }}-
+            composer-${{ runner.os }}-${{ matrix.php-version }}-
+            composer-${{ runner.os }}-
+            composer-
+
+      - name: Install dependencies
+        run: |
+          composer update --no-interaction --prefer-dist --no-progress ${{ matrix.dependencies }}
+
+      - name: Run tests
+        run: |
+          vendor/bin/phpunit

.travis.yml

@@ -16,14 +16,21 @@ env:
 matrix:
     include:
         - php: 7.2
-        - php: 7.3
-        - php: "7.4snapshot"
+          env: PHPUNIT_FLAGS='--coverage-clover clover'
         - php: 7.2
           env: COMPOSER_FLAGS='--prefer-lowest --prefer-stable'
         - php: 7.2
           env: TARGET=docs
         - php: 7.2
           env: TARGET=cs
+
+        - php: 7.3
+        - php: 7.4
+
+        - php: 7.4
+          env: VERY_LATEST=1
+        - php: 8.0snapshot
+          env: COMPOSER_FLAGS='--ignore-platform-req=php'
     fast_finish: true
 
 install:

.travis/install_test.sh

@@ -4,8 +4,8 @@ set -ex
 
 composer self-update
 
-if [[ $TRAVIS_PHP_VERSION  = '7.2' ]]; then PHPUNIT_FLAGS="--coverage-clover clover"; else PHPUNIT_FLAGS=""; fi
 if [[ $TRAVIS_PHP_VERSION != '7.2' ]]; then phpenv config-rm xdebug.ini || true; fi
-if [[ $TRAVIS_PHP_VERSION == '7.4'* ]]; then composer require --dev --no-update "symfony/cache:^4.4@dev"; fi
+
+if [[ $VERY_LATEST == '1' ]]; then composer remove --dev doctrine/phpcr-odm --no-update -n; fi
 
 composer update $COMPOSER_FLAGS -n

README.md

@@ -1,6 +1,5 @@
 # jms/serializer 
 
-
 [![Build status][Master image]][Master] 
 [![Coverage Status][Master coverage image]][Master coverage] 
 

UPGRADING.md

@@ -6,7 +6,7 @@ Upgrading from 2.x to 3.x should require almost no effort.
 The only change is the revert of "deeper branch group exclusion strategy" introduced in 2.0.0 and now reverted as it
 was in 1.x. If you are not using this feature, then upgrading requires no changes at all.
 
-The deprecations introduced in 2.x are still present in 3.0.0, said features are most likley to be removed in an next major. 
+The deprecations introduced in 2.x are still present in 3.0.0, said features are most likely to be removed in the next major version. 
 
 From 1.x to 3.0.0
 =================
@@ -81,7 +81,7 @@ If you are on version `1.x`, it is suggested to migrate directly to `3.0.0` (sin
 
 
 
-**Deprecations** (will be removed in 3.0)
+**Deprecations** (will be removed in 4.0)
 
 - `JsonSerializationVisitor::setData` will be removed, 
   use `::visitProperty(new StaticPropertyMetadata('', 'name', 'value'), 'value')` instead 

composer.json

@@ -16,38 +16,36 @@
         }
     ],
     "require": {
-        "php": "^7.2",
-        "jms/metadata": "^2.0",
+        "php": "^7.2||^8.0",
         "doctrine/annotations": "^1.0",
         "doctrine/instantiator": "^1.0.3",
-        "hoa/compiler": "^3.17.08.08"
+        "doctrine/lexer": "^1.1",
+        "jms/metadata": "^2.0",
+        "phpstan/phpdoc-parser": "^0.4"
     },
     "suggest": {
-        "symfony/yaml": "Required if you'd like to use the YAML metadata format.",
+        "doctrine/cache": "Required if you like to use cache functionality.",
         "doctrine/collections": "Required if you like to use doctrine collection types as ArrayCollection.",
-        "doctrine/cache": "Required if you like to use cache functionality."
+        "symfony/yaml": "Required if you'd like to use the YAML metadata format."
     },
     "require-dev": {
         "ext-pdo_sqlite": "*",
-        "twig/twig": "~1.34|~2.4",
+        "doctrine/coding-standard": "^8.1",
         "doctrine/orm": "~2.1",
-        "jackalope/jackalope-doctrine-dbal": "^1.1.5",
+        "doctrine/persistence": "^1.3.3|^2.0|^3.0",
         "doctrine/phpcr-odm": "^1.3|^2.0",
+        "jackalope/jackalope-doctrine-dbal": "^1.1.5",
+        "ocramius/proxy-manager": "^1.0|^2.0",
+        "phpunit/phpunit": "^8.0||^9.0",
         "psr/container": "^1.0",
-        "symfony/dependency-injection": "^3.0|^4.0",
-        "symfony/yaml": "^3.3|^4.0",
-        "symfony/translation": "^3.0|^4.0",
-        "symfony/validator": "^3.1.9|^4.0",
-        "symfony/form": "^3.0|^4.0",
-        "symfony/filesystem": "^3.0|^4.0",
-        "symfony/expression-language": "^3.0|^4.0",
-        "phpunit/phpunit": "^7.5||^8.0",
-        "doctrine/coding-standard": "^5.0"
-    },
-    "conflict": {
-        "hoa/core": "*",
-        "hoa/consistency": "<1.17.05.02",
-        "hoa/iterator": "<2.16.03.15"
+        "symfony/dependency-injection": "^3.0|^4.0|^5.0",
+        "symfony/expression-language": "^3.0|^4.0|^5.0",
+        "symfony/filesystem": "^3.0|^4.0|^5.0",
+        "symfony/form": "^3.0|^4.0|^5.0",
+        "symfony/translation": "^3.0|^4.0|^5.0",
+        "symfony/validator": "^3.1.9|^4.0|^5.0",
+        "symfony/yaml": "^3.3|^4.0|^5.0",
+        "twig/twig": "~1.34|~2.4|^3.0"
     },
     "autoload": {
         "psr-4": {
@@ -59,9 +57,12 @@
             "JMS\\Serializer\\Tests\\": "tests/"
         }
     },
+    "config": {
+        "sort-packages": true
+    },
     "extra": {
         "branch-alias": {
-            "dev-master": "3.2-dev"
+            "dev-master": "3.10-dev"
         }
     }
 }

doc/conf.py

@@ -6,7 +6,7 @@
 
 # Add any Sphinx extension module names here, as strings. They can be extensions
 # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-extensions = ['sensio.sphinx.refinclude', 'sensio.sphinx.configurationblock', 'sensio.sphinx.phpcode']
+extensions = ['sensio.sphinx.configurationblock', 'sensio.sphinx.phpcode']
 
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']

doc/configuration.rst

@@ -75,7 +75,7 @@ are located::
 
 The serializer would expect the metadata files to be named like the fully qualified class names where all ``\`` are
 replaced with ``.``. So, if you class would be named ``Vendor\Package\Foo``, the metadata file would need to be located
-at ``$someDir/Vendor.Package.Foo.(xml|yml)``. For more information, see the :doc:`reference <reference>`.
+at ``$someDir/Vendor.Package.Foo.(xml|yml)``. If not found, ``$someDir/Vendor.Package.(xml|yml)`` will be tried, then ``$someDir/Vendor.Package.(xml|yml)`` and so on. For more information, see the :doc:`reference <reference>`.
 
 Setting a default SerializationContext factory
 ----------------------------------------------

doc/cookbook/exclusion_strategies.rst

@@ -272,12 +272,16 @@ Dynamic exclusion strategy
 If the previous exclusion strategies are not enough, is possible to use the ``ExpressionLanguageExclusionStrategy``
 that uses the `symfony expression language`_ to
 allow a more sophisticated exclusion strategies using ``@Exclude(if="expression")`` and ``@Expose(if="expression")`` methods.
+This also works on class level, but is only evaluated during ``serialze`` and does not have any effect during ``deserialze``.
 
 
 .. code-block :: php
 
     <?php
 
+    /**
+     * @Exclude(if="true")
+    */
     class MyObject
     {
         /**
@@ -314,7 +318,7 @@ By default the serializer exposes three variables (`object`, `context` and `prop
 
 .. code-block :: php
 
-        <?php
+    <?php
 
     class MyObject
     {
@@ -324,9 +328,35 @@ By default the serializer exposes three variables (`object`, `context` and `prop
         private $name;
 
        /**
-         * @Exclude(if="someMethod(object, context, property_metadata)")
+         * @Expose(if="someMethod(object, context, property_metadata)")
          */
         private $name2;
     }
 
 .. _GroupExclusionStrategy: https://github.com/schmittjoh/serializer/blob/master/src/Exclusion/GroupsExclusionStrategy.php
+
+Using dynamic excludes on class level is also handy when you need to filter out certain objects in a collection, for example based on user permissions.
+The following example shows how to exclude `Account` objects when serializing the `Person` object, if the `Account` is either expired or the user does not have the permission to view the account by calling `is_granted` with the `Account` object.
+
+.. code-block :: php
+
+    <?php
+
+    class Person
+    {
+        /**
+         * @Type("array<Account>")
+         */
+        public $accounts;
+    }
+
+    /**
+     * @Exclude(if="object.expired || !is_granted('view',object)")
+     */
+    class Account
+    {
+        /**
+         * @Type("boolean")
+         */
+        public $expired;
+    }

doc/handlers.rst

@@ -78,3 +78,8 @@ Also, this type of handler is registered via the builder object::
         })
     ;
 
+Skippable Subscribing Handlers
+-------------------------------
+
+In case you need to be able to fall back to the default deserialization behavior instead of using your custom
+handler, you can simply throw a `SkipHandlerException` from you custom handler method to do so.