<p dir="ltr">That assumption didn't seem to work well with the current implementation of the upload feature, where it works in the tests and it doesn't in "real life" ☺</p>
<br><div class="gmail_quote">On Tue, May 12, 2015, 13:46 Aline Manera <<a href="mailto:alinefm@linux.vnet.ibm.com">alinefm@linux.vnet.ibm.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 12/05/2015 13:44, Crístian Deives wrote:<br>
> On 12-05-2015 13:11, Aline Manera wrote:<br>
>> On 12/05/2015 12:46, Crístian Deives wrote:<br>
>>> Shouldn't the UI be updated to re-enable file uploads now?<br>
>><br>
>> I am working on UI right now.<br>
>> As upload is current disabled on UI I don't see problems on merge the<br>
>> backend first. Are you agree?<br>
><br>
> Well, there's no problem in merging this code (as in "it won't break<br>
> anything"), but there's no way for anyone to actually test a file<br>
> upload and make sure the code works "in real life" (other than writing<br>
> a test function...). I can't use the REST API via command line because<br>
> this command requires passing a real object instead of JSON data in<br>
> the variable "chunk", and there's no UI to use it as well. So only<br>
> with the UI I'll be able to actually test if the implementation works.<br>
<br>
Well, we have a specific test case to use file upload. So if the test<br>
passes...<br>
<br>
<br>
</blockquote></div>