[DEPS]: Bump inpsyde/wp-translation-downloader from 2.0.4 to 2.1.1

[dependabot]

Bumps inpsyde/wp-translation-downloader from 2.0.4 to 2.1.1.

Release notes

Sourced from inpsyde/wp-translation-downloader's releases.

2.1.1

Fixes

• PluginConfiguration, TranslatablePackageFactory // ensure that directory separator is correctly trimmed on end of directory input.
• Plugin // changed Plugin::ensureDirectories() to Plugin::ensureDirectoryExists(string $dir) and call when iterating over TranslatablePackage. Relates to: #29
• Downloader // use the "updated" date for translations as filemtime() on cached ZIP files.. Ensure that updated zip files are downloaded again. Relates to: #30

Improvements

• Unzipper // only write information about "falling back from unzip to ZipArchive" and vise versa when running in verbose mode.
• workflows/behat // make use of ramsey/composer-install@v1. upgrade actions/checktout to v3, add --colors to behat call.
• tests // moved "features" into "tests/Behat"-folder. Moved FeatureContext into Inpsyde\WpTranslationDownloader-namespace.

2.1

Locker

This release introduces the Util\Locker-class, which will generate on installation a wp-translation-downloader.lock-file to keep track of the installated translations. On next run it will check against the lock file and only download newer translation files.

Related issues: #9 #26 Read more: https://github.com/inpsyde/wp-translation-downloader/blob/master/docs/Locker.md

Custom composer types and directories

This release will allow you to configure in your wp-translation-downloader.json the directories.names and directories.types mapping with a sub-folder name. This will also open this package to install every Composer type available, instead of just the pre-defined static ones included in this package.

The configuration key directory is now deprecated and will be removed in future. Please make sure to update your configuration to the new key languageRootDir.

Related issues: #13 #27 Read more: https://github.com/inpsyde/wp-translation-downloader/blob/master/docs/Configuraton.md#languagerootdir-and-directories

Support for root package

The root package, which contains the wp-translation-downloader-configuration, is now also added to the list of packages to process.

Related issue: #25 #27

JSON Schema validation

When loading the wp-translation-downloader-configuration, we will now use https://json-schema.org/ to validate the file by using justinrainbow/json-schema, which is included in Composer.

The PluginConfigurationBuilder::build() will now return null when the JSON Schema does not validate successfully against the input and print out information about the errors.

Related issue: #28

Changes under the hood

This release contains a few changes under the hood, including some refactored code and simplifications:

• Removed Inpsyde\WpTranslationDownloader\Io - instead Composer\IO\IOInterface is now used.
• Introduced a new TranslateablePackage and TranslatablePackageInterface which replaces the specific implementations of WpCorePackage, WpThemePackage, WpPluginPackage, LibraryPackage and the TranslatablePackageTrait.
• Plugin will now not create services on activate(). Instead a new method Plugin::bootstrap() was implemented and is being used in the event callbacks to instantiate the Services late.

... (truncated)

Commits

• 72ab08b phpcs..
• ad31a73 Downloader // use the "updated" date for translations as filemtime(). Ensure ...
• 37929ef Unzipper // only write information about falling back from unzip to ZipArchiv...
• 66d4645 behat.yml // fix behat call.
• 44555e6 behat.yml // formatting.
• 78b03e7 workflows/behat // make use of ramsey/composer-install@v1. upgrade actions/ch...
• 4720037 tests // moved "features" into "tests/Behat"-folder. Moved FeatureContext int...
• 098c713 PluginConfiguration, TranslatablePackageFactory // ensure that directory sepa...
• 050c8fd Downloader // removed unused "use".
• d9a213d Merge pull request #28 from inpsyde/feature-json-schema
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)