Sébastien Lorber

Haha exactly, this is what I thought. Nice try but your idea seems to work only when you have a single component unfortunatly :(

props is just not manageable for my very large SPA :( I'll have to reload the full page for now :(

I've found a workaround: https://github.com/facebook/react/issues/3038#issuecomment-76449195 :)

@sebmarkbage agree with that solution. Since React has contextTypes for each componant using context you could easily know which components to re-render. @eplawless have you checked my workaround here? https://github.com/facebook/react/issues/3038#issuecomment-76449195...

I had the same problem in a multi-module project with 1.5.2: ``` lazy val stampleRootProject = Project(id = "stample",base = file("."),settings = commonSettings) .aggregate(stampleWebProject) .settings( aggregate in run := true...

oooh ok thank you, didn't know that. So the effective version of my sbt jar have no impact, it's the target sbt version of the project and the retrocompatibility stuff...

Is this the error you got? > Cannot read property 'Key' of undefined https://github.com/shallwefootball/upload-s3-action/issues/27 Also, are you sure `s3:ListObjects` exists? I get an error with this specific action (which I'd...

I'm using "s3:*" and it does not work either. I believe this action fails because it tries to force `public-read` on the uploaded files, while I don't allow public reads...

So I can confirm, and my minimal bucket ACL looks like this to make this action work: ```json { "Version": "2012-10-17", "Id": "", "Statement": [ { "Sid": "", "Effect": "Allow",...

thanks :) will look at providing a cancel method