Closed (fixed)
Project:
Commerce Discount
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2015 at 17:21 UTC
Updated:
3 Sep 2015 at 04:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gaydamaka commentedComment #3
joelpittetWe have tests now, changing to Needs Review to get testbots opinion on the patch.
Comment #4
joelpittetThis was a performance improvement for clearing cache because install_helper is called when clearing cache too.
Comment #5
joelpittetNot against this patch, it's has some promise! thanks for posting @gaydamaka
Comment #6
gaydamaka commentedComment #7
gaydamaka commentedComment #8
br0kenUsed it on my a project - works really good! Let's have it merged.
Comment #9
joelpittetAll good with committing this without the field_info_cache_clear() call.
Question: Is there something wrong with this logic for it to be removed? Again this also is called on cache flushes so it likely needs to stay.
Comment #10
gaydamaka commentedComment #11
gaydamaka commentedComment #12
br0kenWant to see it merged.
Comment #13
joelpittetWould have been nice if you two addressed my questions in #9 instead of throwing patches and RTBCing them. If just to instill a bit more confidence behind the patch.
Though I've thoroughly reviewed all the code paths in the changes and there should be no unforeseen problems with the latest.
Was a bit hesitant on the multiple
isset()call change there at first too, because it's uncommon in core and could be seen as hard to read unless you know thatisset()with multiple arguments returns FALSE on the first FALSE value and is short circuited the same as the||operator would.Committed and pushed to latest dev branch.
Comment #15
joelpittet