users should be able to upload their composer.lock

[pborreli]

in that case, we could jump directly to the ServeVendorStep step if this composer.lock had been previously served or use a new one named ComposerInstallStep which will be faster than ComposerUpdateStep

[youbs]

Do we use another form action and another consumer?

[pborreli]

I would say no and no :) but not same step as we don't need to composer update but composer install instead

[youbs]

No we don't use another form/consumer, so we use the same ones?

I was about to make another one because the steps differs, luckily I asked you :)
How do you see it then? more precisely, how do we use some other steps regarding what we uploaded?

[youbs]

In fact, I was about to modify the controller, and call "createAndPublish" on the backend with two different set of parameters, depending on when we had the composer.json or the composer.lock, and create two different consumer to handle that. I would have added the ComposerInstallStep instead of the ComposerUpdateStep one (and removed the steps we don't need).

So, is this a mistake?

There is still the issue of the UX. Will #79 be merged or not, etc. If so, then do we add a tab for the composer.lock?

But you know what, we''ll talk about that when you come back :)