Jan Küster

Hm but there is also > invalid_token The access token provided is expired, revoked, malformed, or invalid for other reasons. The resource SHOULD respond with the HTTP 401 (Unauthorized) status...

@jorenvandeweyer done

Also the README should add a "migrate from 3.x" guide, even if there are no breaking issues

@HappyZombies @jorenvandeweyer I have fiddled around with RST but it's a real struggle :see_no_evil: My proposal would be: - use a markdown template and update all guides to markdown-based -...

@jorenvandeweyer sounds promising! We can try to work on this on a separate branch. Does it support jsDoc?

I think we are good with the current docs for now but in the long run jsDoc is a good way for API docs as the functions are documented in...

Hi I ran over the same issue (I usually update all packages when there is a breaking change in the meteor core as in 1.6.1) It broke all my tests...

Even easier would be to just pass the Upload context from `insert`: ``` picture: { type: String, autoform: { afFieldInput: { type: 'fileUpload', collection: 'Images', hooks: { onUpload: (file, uploadCtx)...

There is a new development branch called [multifile](https://github.com/VeliovGroup/meteor-autoform-file/tree/multifile) on which the multiple files upload has been implemented. **!!! Note, that the feature under construction and should not be used in...

Thanks a lot for the investigation. I will look into it and update the branch accordingly.