The validation console command runs checks for:
- manifest files
- translation files
- configuration files
and checks that those files are correct and can be used with the App Orchestration Platform (ACP).
You can run all at once or separated.
vendor/bin/acp app:validate
The command offers the following configuration.
vendor/bin/acp app:validate -m path/to/manifest/files
vendor/bin/acp app:validate -c path/to/configuration/file/configuration.json
vendor/bin/acp app:validate -t path/to/translation/file/translation.json
vendor/bin/acp app:manifest:validate
The command offers the following configuration.
vendor/bin/acp app:manifest:validate -m path/to/manifest/files
vendor/bin/acp app:configuration:validate
The command offers the following configuration.
vendor/bin/acp app:configuration:validate -c path/to/configuration/file/configuration.json
NOTE
This validation needs the context of the manifest files to get locales you want to support and the configuration file that contains fields that need translations.
vendor/bin/acp app:translation:validate
The command offers the following configuration.
vendor/bin/acp app:translation:validate -m path/to/manifest/files
vendor/bin/acp app:translation:validate -c path/to/configuration/file/configuration.json
vendor/bin/acp app:translation:validate -t path/to/translation/file/translation.json
The channel name validation console command runs checks for channel names configured in Project configuration.
vendor/bin/acp acp:channel-name:validate
The command offers the following configuration.
vendor/bin/acp app:translation:validate -c path/to/project/configuration/file/configuration.php