simo

Hmm wait. All my paths are actually symbolic links, so the actual paths are as follows: ``` mighty@sky:/media/SSD/Dropbox/code/modules/sql-admin$ mighty@sky:/media/SSD/node_modules$ ``` So they are in fact under the same directory. Anyway,...

Ok, so it seems that only the `~.node_modules` path isn't working. It seems that the entry point (my example file) **1** (which is also located in a symbolic link location)...

I think another way of solving this is by using the random provider with a keeper: ```tf resource "random_string" "name" { length = 8 special = false upper = false...

I followed the manual install instructions, but I also updated the `metadata.json` file to include `40.4.0` in it. Also extensions are now being enabled through the `Extensions` app instead of...

``` js request.post({ headers: {'content-type': 'multipart/form-data; boundary=WebKitFormBoundaryCIkXuNWC8OhEuT3S'} }) ```

Right that's for [multipart/related](https://github.com/request/request/blob/master/lib/multipart.js#L59) I was thinking about something else. No idea how to change that for `multipart/form-data` although it should be possible, probably.

Just a question: why is this module supposed to be a polyfill for the browser's FormData class? That scenario would be possible to use only via Browserify, Webpack or something...

@alexindigo not a problem. I'm also not against the polyfill, I just want the generation logic as a separate module :) Here are a few `form-data` related tests in request...

I see, good point. Either error message or stringify should be ok. And yet, why is the number stringified then? The number is received as a string on the server,...

Got it. From the server's perspective the stringified `true` and `false` words may be too opinionated, like for example if the client is written in Python, these values may as...