Closed TimKardol closed 2 weeks ago
Coverage report for commit: c4697a8
File: coverage.xml
Cover ┌─────────────────────────┐ Freq.
0% │ ███████████████████████ │ 72.5%
10% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 2.5%
20% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 1.7%
30% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 3.0%
40% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 0.8%
50% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 0.8%
60% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 0.8%
70% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 1.7%
80% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 0.8%
90% │ █░░░░░░░░░░░░░░░░░░░░░░ │ 2.1%
100% │ █████░░░░░░░░░░░░░░░░░░ │ 13.1%
└─────────────────────────┘
*Legend:* █ = Current Distribution
:robot: comment via lucassabreu/comment-coverage-clover
Acceptance env. threw this when testing there - not sure if it's applicable for production env.
Acceptance env. threw this when testing there - not sure if it's applicable for production env.
If this issue occurs when Elio is hosting what needs to be done is to add to php config file (or create additional one) extension=imagick
; might also need to add then "ext-imagick": "*"
to the composer.json
but I am not sure. If you change the composer.json
don't forget to update the composer.lock
:)
Acceptance env. threw this when testing there - not sure if it's applicable for production env.
If this issue occurs when Elio is hosting what needs to be done is to add to php config file (or create additional one)
extension=imagick
; might also need to add then"ext-imagick": "*"
to thecomposer.json
but I am not sure. If you change thecomposer.json
don't forget to update thecomposer.lock
:)
When you add something to the composer file and then run composer install
should it not automatically add it to the lock file? Or is it just to make sure that it actually populates it?
Acceptance env. threw this when testing there - not sure if it's applicable for production env.
If this issue occurs when Elio is hosting what needs to be done is to add to php config file (or create additional one)
extension=imagick
; might also need to add then"ext-imagick": "*"
to thecomposer.json
but I am not sure. If you change thecomposer.json
don't forget to update thecomposer.lock
:)When you add something to the composer file and then run
composer install
should it not automatically add it to the lock file? Or is it just to make sure that it actually populates it?
I am not sure to be honest, but I believe it is depending on the way you add in to the composer file - if you manually add it to the composer.json
then the lock file will become outdated and conflict will occur. But if you require
the package, then it should automatically handle it.
I will merge as soon as the merge conflicts are gone
I will merge as soon as the merge conflicts are gone
Fixed the conflicts, though did not test since I am at work, but it should be working as expected.
Reverts HZ-HBO-ICT/it-conference#568