The POST Create API

Hey Anthony R.

Congrats on being a premiun user!
About your question. I found this very interesting article about incremental ID's vs UUID's https://medium.com/@Mareks_082/auto-increment-keys-vs-uuid-a74d81f7476a
you may want to read it
If you are using MySql and Doctrine 2, this is how you can use UUID's as primary key

// SomeEntity.php
    /**
     * @ORM\Id
     * @ORM\GeneratedValue(strategy="UUID")
     * @ORM\Column(name="id", type="guid")
     */
    private $id;

Cheers!

Hey Remus M.!

Excellent question! I have few points / questions that will hopefully help you out!

1) Where does the cityImage variable come from exactly? Are you reading it from the file input?
2) If you're sending data using FormData, then I believe that this looks like a normal "form submit" to Symfony. In other words, no, you're not sending things via JSON, and so you will not be reading things via $request->getContent(). Instead, you'll be reading things from the POST fields directly - e.g. $form->request->get('cityName'). However, if you're using the form system, then using $form->handleRequest($request) may not work either (depends on your setup) as Symfony forms usually expects your POST data to be under a namespace - e.g. field named like product[field-name] - not just field-name. However, the error you're getting doesn't quite make me think this is the problem.
3) When you submit, if you dump($request->files->all()) what does it look like?

Basically, for the form upload to work, we need to make sure that the data is being sent up to the server correctly, and that we're finding it in the correct location. In general, the "This value is not valid" is being caused by a "data transformer" on one of your fields (you can see exactly which field in the profiler - it may be attached to the "top level form" or a specific field - and exactly where the field is attached is important). Basically, many field types have built in "sanity" validation - and this is the validation error you're using. For example, if you have a "date" input field, and you submit a string that is not a valid date, you would see this error. In your case, it's a signal that some data is not being sent or received correctly. Again, exactly which field (or it could be on the form itself) has this error is important.

By the way, in a true JSON API, file uploads can be handled in a variety of different ways, but here are a few common examples:

1) Make an endpoint where you literally send ONLY the contents of the file as the entire body of the request. Then, $request->getContent() is literally the file contents. It's kind of a pure "API" endpoint to send data for single file. But, you can only send that one thing - you can't send 10 pieces of data, where 1 of them is a file.

2) Send a JSON string like normal, but for the "cityImage" field, make it be the base64 encoded content of your file. On the server, read this, base64 decode it and... you've got your file! You can see an example of this in GitHub's API: https://developer.github.com/v3/repos/contents/#create-a-file

Let me know what you find out - I hope this helps :).

Cheers!

I have tried the first solution and it works if I acces the file like this:
$data = $request->files->all();
dump($data["field-name"]); // object with all the file info

$request->getContent() is empty.

Thank you for help.

Yo Remus M.!

Hmm, interesting! Well, it all depends on exactly *how* your JavaScript upload code looks, but if you've got it working, GREAT!

Cheers!

Yep - sorry about that Stephane! This was an accident actually - I didn't discover my mistake until that chapter :).