Pavel Pravosud
Pavel Pravosud
I don't get the usecase for that. Why would someone set the same value in the same block twice? Also, I'd expect it to overwrite the previous value instead of...
Interesting. Could you a write a spec reproducing the problem?
I'll try to take a look later today. I think I have an idea what might be going on there and what would be the easiest way to fix it.
I haven't really touched rails since 4.0 I think so I'm not very equipped to debug the stuff. If you have found the issue, mind sending a pull request?
Any reason this drops 3.1 support? It seems to be that it should be pretty straightforward to retain it. Edit: Oh nevermind, actually read your PR comment, lol. 🤦♂️
Well, @vincentwoo is right. Currently caching provides benefits only when it allows to skip some of AR queries or you're using really computionally heavy view helpers. When you already have...
Not that I'm aware of. I keep this issue open to remind me to update README.
@droberts84 @xinuc I think the main problem is not Jbuilder, but the total absence of partial caching API for JSON.
Parsing JSON string and merging it doesn't make too much sense because it's even slower than existing caching workflow we have right now.
I'm skeptical about this approach for various reasons. First, seems it's going to increase code complexity quite a lot to make it work with all possible cases, like calling cache...