Search by

pierre-arthur / sylius-upgrade-analyzer

pierrearthurdemengel

Outil CLI d'audit automatisé de migration pour projets Sylius 1.x vers 2.x

Package info

github.com/pierrearthurdemengel/sylius-upgrade-analyzer

Homepage

pkg:composer/pierre-arthur/sylius-upgrade-analyzer

Statistics

Installs: 99

Dependents: 0

Suggesters: 0

Stars: 7

Open Issues: 5

v2.5.0 2026-11-04 17:05 UTC

README

Packagist Version Analyzes Sylius Any project PHP version CI Coverage License

Automated migration audit & auto-fix CLI for Sylius 1.x to 2.x projects.

Sylius Upgrade Analyzer scans your existing Sylius 1.x project, detects every breaking change, deprecated API, and incompatible pattern, then produces a detailed migration report with time estimates, fix suggestions, and 37 automatic corrections covering the most common migration tasks.

Coverage is built from the official UPGRADE-2.0.md, UPGRADE-API-2.0.md, and CHANGELOG-2.0.md. Nothing is left unchecked.

Compatibility

Supports every Sylius 1.x release, from 1.0 to 1.14 LTS (the final 1.x version). There is no Sylius 1.15 or 1.16: 1.14 is the last release of the 1.x branch. The default migration target is Sylius 2.2.

Works whatever your project's PHP version. The Docker image ships its own PHP, so a Sylius 1.x shop still running PHP 7.4 or Symfony 5.4 can be audited without installing anything in the project (see Installation).

Sylius 1.14 LTS security support ends in December 2026. Maintenance already ended in December 2025; after the end of support, 1.x shops no longer receive security fixes (official release cycle). Auditing now is the first step to plan the move to Sylius 2.

Features

49 Built-in Analyzers

Templates & Frontend (6)

# Analyzer What it detects
1 Twig Template Override Overridden Sylius templates to migrate to Twig Hooks
2 Sonata Block Event sonata_block_render_event() / sylius_template_event() to replace with hook()
3 Semantic UI Semantic UI CSS classes in templates (removed in 2.x)
4 jQuery jQuery / Semantic UI JS usage in assets
5 Webpack Encore webpack.config.js + @symfony/webpack-encore detection
6 Use Webpack Config Removed use_webpack from sylius_ui config

Deprecations & Breaking Changes (34)

# Analyzer What it detects
7 Winzou State Machine winzou/state-machine-bundle to Symfony Workflow
8 SwiftMailer swiftmailer/swiftmailer to symfony/mailer
9 User Encoder security.encoders and getSalt() methods
10 Payum Payum gateways convertible to Payment Requests (optional: Payum is still supported, not counted in the effort)
11 Message Bus Rename sylius_default.bus / sylius_event.bus renames
12 Command Handler Rename References to Sylius Message* namespaces renamed Command*
13 Deprecated Email Manager Removed OrderEmailManager / ContactEmailManager
14 Removed Payment Gateway Stripe / PayPal Express removed from core
15 Service Decorator Decorators targeting renamed Sylius services
16 Order Processor Autoconfiguration Order processors and cart contexts no longer registered through their interface
17 Removed Form Type Extension Classes and services built on form extensions removed from Sylius core
18 Behat Context Deprecation Removed sylius.behat.api_security service
19 Admin Menu Event Listeners on the five admin menus removed in 2.0
20 Promotion Rule Checker PromotionRuleCheckerInterface changes
21 Shipping Calculator References to the renamed core shipping calculator services
22 Doctrine XML Mapping *.orm.xml to PHP attribute migration
23 Custom Fixture Fixture system changes
24 Multi-Store Channel Removed findOneByHostname(), custom channel and locale contexts
25 Bundle Configuration 7 removed bundles + 6 required new bundles in bundles.php
26 Calendar to Clock sylius/calendar to symfony/clock (ClockInterface)
27 Security Firewall new_api_admin_user / new_api_shop_user firewall renames
28 User Model Field Removed locked, expiresAt, credentialsExpireAt, \Serializable
29 Removed Class 150+ removed classes (Templating Helpers, UiBundle, DataCollectors, etc.)
30 Renamed Service ID 21 renamed/removed Sylius service IDs
31 Removed Route 43 removed admin/shop routes (partials, AJAX, etc.)
32 LiipImagine Config Resolver/loader "default" to "sylius_image"
33 Constructor Signature 24 classes with changed constructor signatures
34 PHP Node Version PHP 8.2+, Node.js 20+, Symfony 5.4 detection
35 Class Move 14 classes moved between bundles
36 Service Visibility Direct $container->get('sylius.*') calls (now private)
37 Payment Request Env Missing Messenger transport env vars for payments
38 Deprecated Bundle Package 7 removed packages (FOSRest, JMSSerializer, BazingaHateoas, etc.)
39 Removed Config Key Removed YAML config keys (sylius_core.*, sylius_api.*, MongoDB/PHPCR ODM)
40 Routing Import Legacy routing imports (Payum shop routes, API route parameter renames)

Plugins (1)

# Analyzer What it detects
41 Plugin Compatibility Sylius plugins cross-referenced with Addons Marketplace + Packagist

Grid & Resource (3)

# Analyzer What it detects
42 Grid Customization Custom grid YAML + PHP grid classes + custom columns/filters
43 Resource Bundle SyliusResourceBundle config, custom factories/repositories
44 Grid Filter Entity type: entities to type: entity, field: to fields: syntax

API Platform (4)

# Analyzer What it detects
45 API Platform Migration @ApiResource, DataProvider/DataPersister, ApiPlatform\Core namespace
46 API Serialization Group Missing sylius: prefix on serialization groups
47 API Endpoint Restructure 8+ restructured/removed API endpoint paths
48 API Query Extension Signature $operationName to Operation $operation parameter change

Security (1)

# Analyzer What it detects
49 PHP Security Patch PHP versions declared by the project (Dockerfile, compose, config.platform.php, .php-version, .tool-versions) that miss a security release, e.g. the October 2026 remote code execution fixes (CVE-2026-109618, CVE-2026-109619)

6 Output Reporters

  • Console -- Rich terminal output with ASCII gauge, colored severity levels, category breakdown
  • JSON -- Machine-readable structured report
  • CSV -- Excel-compatible export (UTF-8 BOM, semicolon separator) via --format=csv
  • SARIF -- Static Analysis Results Interchange Format (GitHub Code Scanning compatible)
  • Markdown -- Human-readable report with tables, suitable for PRs and wikis
  • PDF -- Stakeholder report generated locally: executive summary, risk factors, roadmap, budget estimate (--tjm) and detailed issues (requires dompdf/dompdf)

37 Auto-Fixers

Fixer Confidence What it fixes
API Endpoint Restructure Fixer HIGH Replaces 3 API endpoint paths renamed in UPGRADE-API-2.0.md
Bundle Configuration Fixer HIGH Removes bundles dropped by Sylius 2.0 and adds the new ones in bundles.php
Calendar to Clock Fixer HIGH DateTimeProviderInterface → ClockInterface, sylius/calendar → symfony/clock
Class Move Fixer HIGH Updates FQCN references of classes moved between Sylius bundles
Command Handler Rename Fixer HIGH Sylius Message* namespaces → Command* (your own code is not renamed)
Deprecated Bundle Package Fixer HIGH Removes deprecated packages from composer.json, keeping the JSON valid
Grid Filter Entity Fixer HIGH type: entities → type: entity in grid YAML
LiipImagine Config Fixer HIGH Resolver/loader default → sylius_image
Message Bus Fixer HIGH Renames bus references in YAML and PHP files
Multi-Store Channel Fixer HIGH findOneByHostname() → findOneEnabledByHostname()
Order Processor Autoconfiguration Fixer HIGH Adds #[AsOrderProcessor] / #[AsCartContext] (priority 0, as in 1.x)
Payment Request Env Fixer HIGH Adds the 2 Messenger transport variables of UPGRADE-2.0.md to .env
Removed Config Key Fixer HIGH Comments out removed YAML config keys with TODO markers
Renamed Service ID Fixer HIGH Renames service IDs listed word for word in the UPGRADE-2.0.md tables
Routing Import Fixer HIGH Replaces old routing imports and renamed new_api_* parameters
Security Config Fixer HIGH Generates the security.password_hashers configuration
Security Firewall Fixer HIGH Renames new_api_admin_user → api_admin, new_api_shop_user → api_shop
Shipping Calculator Fixer HIGH Renames references to sylius.shipping_calculator* services (the tag is unchanged)
Use Webpack Config Fixer HIGH Removes use_webpack from sylius_ui YAML config and Twig conditionals
User Encoder Fixer HIGH / MEDIUM YAML: encoders → password_hashers (high); PHP: getSalt() (medium)
API Platform Migration Fixer MEDIUM ApiPlatform\Core → API Platform 3 namespaces
API Query Extension Signature Fixer MEDIUM string $operationName → ?Operation $operation = null + use statement
API Serialization Group Fixer MEDIUM Adds the sylius: prefix to admin: and shop: serialization groups
Constructor Signature Fixer MEDIUM Adds TODO markers on overridden constructors of changed Sylius classes
Deprecated Email Manager Fixer MEDIUM Replaces email manager FQCNs moved to CoreBundle
Promotion Rule Checker Fixer MEDIUM Moves CartQuantityRuleChecker from Promotion to Core namespace
Removed Class Fixer MEDIUM Comments out use statements of removed classes with TODO markers
Removed Payment Gateway Fixer MEDIUM Comments out the whole stripe_checkout / paypal_express_checkout YAML definition
Removed Route Fixer MEDIUM Comments removed route references with TODO markers
Resource Bundle Fixer MEDIUM Comments out PHPCR/MongoDB drivers (doctrine/orm is untouched)
Service Decorator Fixer MEDIUM Renames decorates: targets listed in the UPGRADE-2.0.md tables
Sonata Block Event Fixer MEDIUM sonata_block_render_event() / sylius_template_event() → hook()
SwiftMailer Fixer MEDIUM / LOW YAML: framework.mailer.dsn (medium); PHP: class names only, calls to rewrite (low)
Twig Hook Fixer MEDIUM Registers a Twig Hook for a template override (the hook template is yours to create)
User Model Field Fixer MEDIUM Comments deprecated locked, expiresAt, credentialsExpireAt fields and Serializable
Workflow Migration Fixer MEDIUM Converts winzou state machine YAML to Symfony Workflow config
Doctrine XML Mapping Fixer LOW Adds TODO marker for *.orm.xml to PHP attribute conversion

Every fixer's real before/after output is in docs/fixer-examples.md (replayed by the test suite), and docs/fixers.md explains each confidence level.

GitHub Action

Run the analyzer in your CI pipeline, post PR comments, and upload SARIF to GitHub Code Scanning.

Additional Features

  • Custom rules via .sylius-upgrade-rules.yaml
  • Baseline management -- save and diff results across runs
  • Sprint planner -- generate a migration roadmap with sprint breakdown
  • Plugin compatibility -- checks Sylius Addons Marketplace and Packagist
  • Multi-project analysis -- consolidated comparison table and budget for agencies managing several Sylius projects (console, JSON, Markdown or PDF)
  • Report comparison -- diff two reports to track migration progress
  • Plugin compatibility matrix -- check a list of plugins against the target version

Installation

Pick the mode that fits your project. The first three never touch your project's composer.json.

Docker (recommended for Sylius 1.x projects)

Works whatever your project's PHP version, all formats included (PDF too):

docker run --rm -v "$PWD:/project" ghcr.io/pierrearthurdemengel/sylius-upgrade-analyzer

# Any command and option, reports written next to your code
docker run --rm -v "$PWD:/project" --user "$(id -u):$(id -g)" ghcr.io/pierrearthurdemengel/sylius-upgrade-analyzer \
  sylius-upgrade:analyze /project --format=pdf --output=/project/report.pdf --tjm=600

Standalone PHAR

A single file, no dependency to install. Needs PHP 8.2+ on the machine running it, not in the audited project. PDF output is not available from the PHAR (use Docker for PDF).

curl -LO https://github.com/pierrearthurdemengel/sylius-upgrade-analyzer/releases/latest/download/sylius-upgrade-analyzer.phar
php sylius-upgrade-analyzer.phar sylius-upgrade:analyze /path/to/project

Global Composer install

composer global require pierre-arthur/sylius-upgrade-analyzer
sylius-upgrade-analyzer sylius-upgrade:analyze /path/to/project

Inside the project

Only when the project already runs PHP 8.2+ with Symfony 6.4 or 7.x:

composer require --dev pierre-arthur/sylius-upgrade-analyzer

Professional Migration Services

Sylius Upgrade Analyzer is developed by Pierre-Arthur Demengel, freelance developer specialised in Sylius 1.x to 2.x migrations.

The report tells you what has to change and how long it should take. If you would rather not carry the migration alone:

  • Audit -- review of your report with your team, risks and priorities
  • Fixed-price migration -- the upgrade carried out end to end, from dependencies to production
  • Team support -- guidance on Twig Hooks, Symfony Workflow, Payment Requests and plugin replacements

Get a free migration diagnosis

Usage

Basic Analysis

# Analyze the current directory
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze

# Analyze a specific project
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze /path/to/sylius-project

# Target a specific Sylius version
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --target-version=2.2

Output Formats

# Console output (default)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze

# JSON report
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=json --output=report.json

# SARIF report (for GitHub Code Scanning)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=sarif --output=report.sarif

# Markdown report
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=markdown --output=report.md

# CSV export (Excel-compatible)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=csv --output=report.csv

# PDF report, with a budget estimate based on a 600 EUR daily rate
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=pdf --output=report.pdf --tjm=600

PDF generation is fully local and relies on dompdf, an optional dependency kept out of the default install to avoid version conflicts with your project:

composer require --dev dompdf/dompdf

The budget estimate converts the estimated hours into days on a 7-hour basis, rounded up to the next half day.

Project Naming

# Explicit project name (included in meta.project_name)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --project-name="My Shop"

# Auto-detected from composer.json "name" field or directory name
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze

Filtering Analyzers

# Run only specific analyzers
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --only="Twig Template Override" --only="Payum"

Verbose Output

# Show warnings
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze -v

# Show warnings and suggestions
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze -vv

Offline Mode

# Skip marketplace compatibility checks
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --no-marketplace

Hiding the Migration Services Mention

Console, Markdown and PDF reports end with a one-line mention of the migration services above. JSON, SARIF and CSV outputs never contain it. To remove it:

vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --no-promo

Custom Rules

# Use a custom rules file
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --rules=.sylius-upgrade-rules.yaml

Baseline Management

# Save a baseline
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --save-baseline

# Compare with previous baseline
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --diff

Sprint Planning

# Generate a sprint plan with team velocity of 40h/sprint
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --sprint-plan --velocity=40

Multi-Project Analysis

Audit a whole portfolio of Sylius shops in one run and get a comparison table (complexity, risk, blocking issues, hours, budget) with totals:

# Comparison table in the terminal
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:multi-analyze \
  /path/to/project1 /path/to/project2 /path/to/project3 --tjm=600

# Consolidated PDF (one overview page, then one summary page per project)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:multi-analyze \
  /path/to/project1 /path/to/project2 --format=pdf --output=portfolio.pdf --tjm=600

# Also available: --format=json and --format=markdown

Projects sharing the same Composer name (forks, per-country variants) are told apart by their directory name.

Compare Reports

# Compare two JSON reports (e.g. before and after a migration sprint)
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=json --output=before.json
# ... fix some issues ...
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --format=json --output=after.json
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:compare before.json after.json

Auto-Fix

The analyzer can automatically fix certain issues:

# Apply all available fixes
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --fix

# Preview fixes without modifying files
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --fix --dry-run

Each fix has a confidence level:

  • HIGH -- Safe to apply automatically (e.g., renaming security.encoders to security.password_hashers)
  • MEDIUM -- Likely correct but manual review recommended (e.g., workflow migration)
  • LOW -- Uncertain, manual verification required

In --dry-run mode, the tool generates a unified diff patch showing what would change without writing any files.

What auto-fixes can and cannot do

  • Nothing is written without your consent in a terminal: --fix lists every change and asks for confirmation. In CI (non-interactive), --fix applies directly, as scripts expect. Run --dry-run first to review the patch.
  • Files only: no fixer connects to a database, runs a migration or executes a command. Every write goes through a single place (FixEngine::applyFix()), so every change is visible in your Git diff.
  • Payment configuration is handled conservatively: no fixer edits PHP payment code. One MEDIUM fixer comments out (never deletes) the removed Stripe Checkout and PayPal Express gateway YAML, and one adds the missing Payment Request environment variables to .env. Payum itself is left alone: Sylius 2.0 still supports it.
  • Run it on a clean Git working tree so that git diff and git checkout . remain your safety net.

GitHub Action

Add the analyzer to your CI workflow:

name: Sylius Migration Audit
on: [push, pull_request]

permissions:
  contents: read
  security-events: write   # required by upload-sarif
  pull-requests: write     # required by post-pr-comment

jobs:
  analyze:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: pierrearthurdemengel/sylius-upgrade-analyzer@v2.2.0
        with:
          project-path: '.'
          target-version: '2.2'
          fail-on-breaking: 'true'
          upload-sarif: 'true'
          post-pr-comment: 'true'

Action Inputs

Input Default Description
project-path . Path to the Sylius project
target-version 2.2 Target Sylius version
analyzer-version ^2.2 Composer constraint of the analyzer version to install
fail-on-breaking true Fail the job if breaking issues are found
upload-sarif false Upload SARIF report to GitHub Code Scanning
post-pr-comment false Post a summary comment on the PR (lists up to 50 breaking issues; skipped with a warning on read-only fork tokens)

The analyzer is installed in the runner's temporary directory, so your project's composer.json and dependencies are left untouched.

Action Outputs

Output Description
complexity Detected complexity level (trivial, moderate, complex, major)
total-hours Estimated total hours
breaking-count Number of breaking issues

Custom Rules

Create a .sylius-upgrade-rules.yaml file at the root of your project:

rules:
  - name: legacy_payment_service
    type: php_class_usage
    pattern: 'App\\Service\\LegacyPaymentService'
    severity: breaking
    category: deprecation
    message: 'Legacy payment service must be replaced'
    suggestion: 'Migrate to the new PaymentProcessor service'
    estimated_minutes: 120

  - name: old_twig_filter
    type: twig_function
    pattern: 'sylius_price_format'
    severity: warning
    category: twig
    message: 'Deprecated Twig filter detected'
    suggestion: 'Use the new money_format filter instead'
    estimated_minutes: 15

Supported rule types: php_class_usage, php_method_call, twig_function, yaml_key.

See docs/custom-rules.md for the full reference.

Example Output

Console

 Sylius Upgrade Analyzer - Migration Report
 ===========================================

 Projet        : /home/dev/my-sylius-shop
 Version       : 1.12.18
 Cible         : 2.2
 Date          : 04/04/2026 14:32:07

 Resume global
 -------------
   Problemes critiques (BREAKING) : 12
   Avertissements (WARNING) :        23
   Suggestions :                      8

   Temps total estime : 142.5 heures

   Complexite globale : COMPLEXE

   [████████████████████████████░░░░░░░░░░░░░] 142.5h / COMPLEX

 Estimation par categorie
 -------------------------
 +-----------------+--------------+-----------------+
 | Categorie       | Nb problemes | Heures estimees |
 +-----------------+--------------+-----------------+
 | Deprecations    | 18           | 64.0 h          |
 | Templates Twig  | 7            | 35.0 h          |
 | Front-end       | 6            | 24.0 h          |
 | Plugins         | 4            | 16.0 h          |
 | API             | 2            | 3.5 h           |
 +-----------------+--------------+-----------------+

JSON

{
  "summary": {
    "complexity": "complex",
    "total_hours": 142.5,
    "breaking_count": 12,
    "warning_count": 23,
    "suggestion_count": 8,
    "detected_version": "1.12.18",
    "target_version": "2.2"
  },
  "hours_by_category": {
    "deprecation": 64.0,
    "twig": 35.0,
    "frontend": 24.0,
    "plugin": 16.0,
    "api": 3.5
  },
  "issues": [
    {
      "severity": "breaking",
      "category": "deprecation",
      "analyzer": "Winzou State Machine",
      "message": "3 machine(s) a etats winzou detectee(s) necessitant une migration vers Symfony Workflow",
      "detail": "Chaque machine a etats doit etre convertie en definition Symfony Workflow.",
      "suggestion": "Migrer chaque definition winzou_state_machine vers framework.workflows.",
      "estimated_minutes": 720
    }
  ]
}

Compatibility Matrix

Check the compatibility of Sylius plugins with the target version (Addons Marketplace + Packagist):

# Read the plugins from the composer.json of the current directory
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:matrix

# Check an explicit list, output as Markdown
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:matrix \
  bitbag/wishlist-plugin,sylius/invoicing-plugin --format=markdown

The status of every public Sylius plugin is also published, refreshed weekly, in the Sylius 2 plugin readiness tracker. The method and a snapshot of the data are in the study Sylius plugin ecosystem readiness for Sylius 2 (Zenodo).

Results on Public Projects

The analyzer is run on public Sylius 1.x code bases to check its findings against reality (details and commands in docs/benchmarks.md):

Project Sylius Issues Blocking Estimated effort
Sylius-Standard (1.14 branch, official skeleton) ~1.14.0 66 27 52.0 h
Sylius/InvoicingPlugin (1.0 branch) ~1.13.0 || ~1.14.0 30 6 38.5 h
BitBag SyliusWishlistPlugin ^1.13 || ^1.14 13 2 15.5 h

Every blocking issue on these projects was reviewed by hand. Running these benchmarks already caught and fixed false positives (removed configuration keys, development tools reported as incompatible plugins).

Quality and Safety

  • Tests: 940+ PHPUnit tests, including one replayed before/after example per auto-fixer, line coverage of at least 80 % enforced in CI (the build fails below), PHPStan level 8, PHP CS Fixer.
  • CI matrix: PHP 8.2, 8.3 and 8.4, against Symfony 6.4 and 7.4, dependencies installed from composer.lock, composer audit in every job.
  • Every detection is sourced: checks are traced back to the official Sylius upgrade guides; checks that could not be traced back to a documented change have been removed (see CHANGELOG.md).
  • Semantic versioning and a maintained CHANGELOG.md. Security issues: see SECURITY.md.
  • Privacy: the analysis runs entirely on your machine; your code is never uploaded. The only network calls are optional plugin compatibility checks against the Sylius Addons Marketplace and Packagist (--no-marketplace disables them).

If the tool saved you time, a star on GitHub or a review on the Sylius Addons Marketplace helps other teams find it.

Contributing

Contributions are welcome! Please read CONTRIBUTING.md for guidelines on:

  • Creating custom analyzers
  • Creating custom fixers
  • Coding standards and test requirements
  • PR process

Documentation

License

This project is licensed under the MIT License. See the LICENSE file for details.

Author

Pierre-Arthur Demengel -- freelance developer specialised in Sylius 1.x to 2.x migrations -- pierrearthur.demengel@gmail.com