keulinho

# Best practices and conventions
This guide contains best practices and conventions for building an administration extension.

## Component conventions
 - Each component should be as slim as possible.
 - The component stands for its own and fulfills only one purpose. It is better to make multiple smaller components than putting too much complexity into a single component.
 - The component contains not much logic. Complex logic is handled by the modules.
   
### Properties order
The properties of a component should have the following order:

keulinho

Timeline

• 8:00 CEST/13:00 ICT: Intro
• 8:30 CEST/13:30 ICT: Daily
• 10:30 CEST/15:30 ICT: Review + more info on the Core Team
• 11:00 CEST/16:00 ICT: End

Task

• Work on the following ticket.

keulinho

Currently, we throw some deprecation, which are not solvable. This is useless for external devs and generates useless logs.

Examples:

run bin/console theme:compile

07:32:06 INFO      [php] User Deprecated: Since shopware/core : Class Shopware\Storefront\Event\ThemeCompilerEnrichScssVariablesEvent is deprecated. Use Shopware\Storefront\Theme\Event\ThemeCompilerEnrichScssVariablesEvent instead.
User Deprecated: Since shopware/core : Class "Shopware\Core\Content\Product\SalesChannelProductBuilder" is deprecated and will be removed in v6.5.0.0. Use "AbstractPropertyGroupSorter, AbstractProductMaxPurchaseCalculator, AbstractIsNewDetector" instead.

keulinho

<?php declare(strict_types=1);

use Rector\CodeQuality\Rector\Class_\InlineConstructorDefaultToPropertyRector;
use Rector\Config\RectorConfig;
use Rector\Renaming\Rector\Name\RenameClassRector;
use Rector\Set\ValueObject\LevelSetList;

return static function (RectorConfig $rectorConfig): void {
    $rectorConfig->paths([
        __DIR__ . '/src',