display page with logs of run about composer-service HOT 20 CLOSED

this will depend on #15 refactor

from composer-service.

maybe like travis with a live streamed logfile

from composer-service.

first is wrapping the output, second will be a basic lame implementation, third one will be reactphp

from composer-service.

What do we need to log? Just the output from composer?

from composer-service.

yes see the discussion with @igorw https://twitter.com/igorwhiletrue/status/415159470897909761

from composer-service.

right now we have a way to display information without taking to much space, it's the security vulnerability report (test a composer.json with symfony/routing 2.0.16)

from composer-service.

Something like this?

from composer-service.

The output should be very easy to copy&paste

from composer-service.

@youbs nice yes, instead of "Show composer.lock" i would add "Show installed" with the result of ./composer show --installed
@staabm totally agree

from composer-service.

another representation could be to show each file as a tab.
1st tab composer.json; 2nd composer.lock; 3rd composer output; 4th security report

The tabs 2-4 would be created after clicking "GO"

from composer-service.

from composer-service.

not sure about the position of the Go button now ...

from composer-service.

IMO The tabs will only be rendered after a "GO" click therefore the intial page would looke like it is already rendered..

But it would also fit below the textarea...

Another thing i could think of: make the Go button disapear and add a reset button instead to get back to the initial view

from composer-service.

@staabm would love to see your proposal :) or maybe just a mockup so I can work on a PR

from composer-service.

@youbs what do you think ?

from composer-service.

Will have a look at it tomorrow

from composer-service.

@staabm thanks !

from composer-service.

Tabs are nice!

What about the composer.lock upload @pborreli wanted to do later, would there be the 2 tabs (composer.json, composer.lock) with the 2nd one being empty at the initial page load, and either the user fill it and submit it, or he submits the composer.json and we fill it as soon as we get the result back?

from composer-service.

@youbs well not sure about it right now as we are speaking about it together, I have no closed opinion, just want to go to the more ergonomic / simple solution so feedback are more than welcome :)

from composer-service.

I think there should be a "upload" tab (which can consume composer.json or composer.lock) and all other tabs beside it.
After click on go the upload tab hides and all other tabs get displayed

from composer-service.