grayasfen.blogg.se - Magento devdocs technical guidelines

#MAGENTO DEVDOCS TECHNICAL GUIDELINES CODE#
#MAGENTO DEVDOCS TECHNICAL GUIDELINES DOWNLOAD#

Require inline aliases are not used in the composer.json file.Īdditional requirements for package declarations are applied depending on the package type.Version restriction should be specified according to recommendations. The package does not use * as a version restriction for Magento packages (packages with magento vendor).The package does not declare any of the following packages as a dependency:.The package does not restict a set of compatible PHP versions declared by supported Magento versions.for shared libraries, valid types are: magento2-module, magento2-theme, magento2-language.for themes, valid types is only magento2-theme.for extensions, valid types are: magento2-module, magento2-language, metapackage.The package has valid Composer package type:.Submitted package contains a composer.json file.Submitted package does not exceed 30 MB.

#MAGENTO DEVDOCS TECHNICAL GUIDELINES CODE#

Enforces best practices for Magento code distributionĪny code submitted for technical review at Magento Developers Portal is examined to ensure that:.

Is packaged as a valid Magento module, theme, language package, or meta-package.

See also: Coding Standards Package Validation: verify that submitted code is a valid Magento extension If the submitted code fails to pass the review, a technical report is generated that describes each issue found, and its location in the codebase. The Marketplace coding standard review uses a custom set of coding sniffs.

Packaging Magento Version 1.x ExtensionsĬoding Standards: Check code quality/syntax.

#MAGENTO DEVDOCS TECHNICAL GUIDELINES DOWNLOAD#

To download the tool, see the Marketplace Tools GitHub repository. Required Files Allĭevelopers of Magento 2.x extensions can use the validation tool to test the package before it is submitted to Magento Marketplace. All Magento modules, themes, and language packs must contain a composer.json and registration.php file. The submitted package must be a Magento module, theme, language pack, or metapackage, that meets Composer packaging and format requirements. Validate: Verify package for required files The process also ensures that the package meets Composer packaging and format requirements and Magento coding standards. During technical review, your code is examined to detect the presence of viruses, malware, and any indication of plagiarism.