Closed (fixed)
Project:
Facet API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 May 2011 at 03:21 UTC
Updated:
4 Jan 2014 at 00:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
cpliakas commentedNote that the bundle dependency plugin has some assumptions surrounding the type that need to be broken.
Comment #2
cpliakas commentedComment #3
cpliakas commentedMarking as active. We need to maintain backwards compatibility for this change so that we don't have to synchronize releases with the other backends. This means that the adapter will have both "type" and "types" keys.
Comment #4
cpliakas commentedMarking as a beta4 blocker.
Comment #5
cpliakas commentedAdding new tag to track backwards compatible API changes. Legacy code should be removed when the module goes 1.0.
Comment #6
cpliakas commentedChanged my mind. There are more important fixes that should be released ASAP.
Comment #7
cpliakas commentedFirst crack at resolving this. The known issue is that the bundle is not entity aware. We really need facets that contain bundles a way to identify themselves as such.
Comment #8
cpliakas commentedWebchick says jump, I say "how high?". http://www.webchick.net/node/89
Comment #9
cpliakas commentedResolved in commit 9cc690e. Bundle issue posted at #1222754: Resolve assumptions in the "bundle" dependency plugin.
Comment #10
das-peter commentedJust came across an issue while playing around with the facet_api <-> search_api integration.
The code for the legacy support of the
typekey deletes the whole info array.Attached patch fixes this.
Comment #11
cpliakas commentedOh boy. Great catch! Looks good to me.
Comment #12
cpliakas commentedCommitted at 5be7a86.
Congrats on becoming the 5th committer to Facet API!
Thanks,
Chris