opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Run prettier on all *.md files

Browse source 
```
prettier '{app,source}/**/**.md' --write
```
This commit is contained in:
Oliver Davies 2020-03-08 17:52:59 +00:00
parent a3ceeaf0f3
commit 85a10c545b
170 changed files with 5127 additions and 2282 deletions
Download patch file Download diff file Expand all files Collapse all files

21
source/_posts/drupal-vm-generator-updates.md
View file

@ -4,17 +4,28 @@ date: 2016-12-30
excerpt: I’ve released some new versions of the Drupal VM Generator.
tags: ['drupal-vm-generator', releases]
---
The main updates are:
- Fixed an `InvalidResponseException` that was thrown from within the `boolean_as_string` Twig filter from the opdavies/twig-extensions library when the `config:generate` command was run in non-interactive mode.
- Adding a working test suite for the existing commands, using PhpUnit and Symfony’s Process component. This is now linked to [Travis CI][2], and the tests are run on each commit and pull request.
- The version requirements have been changed to allow 2.7 versions of the used Symfony Components, as well as the 3.x versions. This was done to resolve a conflict when also installing Drush globally with Composer.
- Fixed an `InvalidResponseException` that was thrown from within the
`boolean_as_string` Twig filter from the opdavies/twig-extensions library when
the `config:generate` command was run in non-interactive mode.
- Adding a working test suite for the existing commands, using PhpUnit and
Symfony’s Process component. This is now linked to [Travis CI][2], and the
tests are run on each commit and pull request.
- The version requirements have been changed to allow 2.7 versions of the used
Symfony Components, as well as the 3.x versions. This was done to resolve a
conflict when also installing Drush globally with Composer.
## Next Steps
Currently the project is based on Drupal VM 3.0.0 which is an outdated version ([4.1.0][3] was released today). Adding updates and supporting the newer versions is a high priority, as well as keeping in sync with new releases. This will be easier with the test suite in place.
Currently the project is based on Drupal VM 3.0.0 which is an outdated version
([4.1.0][3] was released today). Adding updates and supporting the newer
versions is a high priority, as well as keeping in sync with new releases. This
will be easier with the test suite in place.
My initial thoughts are that version 2.10.0 will support Drupal VM 4.0.0, and if needed, 2.11.0 will ship shortly afterwards and support Drupal VM 4.1.0.
My initial thoughts are that version 2.10.0 will support Drupal VM 4.0.0, and if
needed, 2.11.0 will ship shortly afterwards and support Drupal VM 4.1.0.
[0]: http://www.drupalvmgenerator.com
[1]: https://github.com/opdavies/drupal-vm-generator/tree/master/tests/Command