#32: File constraints now available on both client and server

[Pagebakers]

Proposed api and usage: (haven't updated the docs yet)

File restrictions, can be configured both on the client and server

Slingshot.fileRestrictions("avatar", {
    allowedFileTypes: ["image/png", "image/jpeg", "image/gif"],
    maxSize: 1*0x400*0x400,
    authorize: function () {
        return this.userId;
    }
});

The directive

Slingshot.createDirective("avatar", Slingshot.S3Storage, {
        key: function (file) {
            return [
                "users",
                this.userId,
                Date.now() + "-avatar." + file.type.split("/")[1]
            ].join("/");
        }
    });

The uploader

    uploader = new Slingshot.Upload("avatar");

    var isValid = uploader.validate(file); // true or instance of Error

    uploader.send(...)

The validate method is also called right before the authorization request method is called.

[gsuess]

I think this API change can be avoided, if the we mix in the file restrictions into options before constructing the directive.

[gsuess]

My bad, this includes the server-request for authorization. I miss-read the diff before and though it was a new status added for the client-side validation step. Lets keep it at "authorizing".

[gsuess]

Remove this param doc.

[gsuess]

Great please update the readme also.

[josebalius]

Has this made it to the repo server? The slingshot version I am using doesn't seem to have the validate method.

[gsuess]

This was released in 0.3.0.

On Thu, 22 Jan 2015 10:48 pm Jose Garcia notifications@github.com wrote:

Has this made it to the repo server? The slingshot version I am using
doesn't seem to have the validate method.

—
Reply to this email directly or view it on GitHub
#35 (comment)
.

[josebalius]

@gsuess I updated to the latest, but validate never returns an error. Is there anyway to debug it further?

[gsuess]

The most likely cause is that you have not declared any fileRestrictions on the client to validate against.