Closed (fixed)
Project:
Facet API
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 May 2013 at 20:10 UTC
Updated:
17 May 2013 at 23:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
nick_vhComment #2
nick_vhComment #3
cpliakas commentedThis overall approach makes sense to me.
Ideally I would like the requirements stuff to be cleaner, but I think you have made it as backwards-compatible and as clean as you possibly can, so I would be in favor of committing this approach to Facet API and improving the over all system in a later major version.
Marking as needs work for a really small reason... in order to be consistent with other keys in the hook_facetapi_widgets() definitions, the "requirements_operator" should be separated by a space and not an underscore.
We should also post a follow-up issue to add tests for the operator.
Great work,
Chris
Comment #4
cpliakas commented#1958362: Implement the ability to customize the date ranges via the UI is dependent on this feature. Marking as a feature because everything works as intended and the API does allow you to create a function that could do this logic, although definitely not ideal.
Comment #5
cpliakas commentedAttached patch makes the suggested change.
Comment #7
cpliakas commentedFailed because it conflicted with patch at #1974058: Include ctools plugins for facetapi_facet_display_form_validate that was committed to all branches of Facet API. Patch re-rolled.
Comment #8
cpliakas commentedCommitted to 7.x versions of Facet API.
http://drupalcode.org/project/facetapi.git/commit/7706951
http://drupalcode.org/project/facetapi.git/commit/f91afec
6.x-3.x backport issue posted to #1986510: Backport adding support for OR logic in requirements.