Change HS API to support lineage storage provided by implementations
crea - June 15, 2009 - 11:22
| Project: | Hierarchical Select |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
Creating this for future reference. Don't have time for this myself, but we need this in case someone would want to work on it.
As stated in #476656: Limitations of lineages and dropbox with multiple parent hierarchies , at the moment HS cannot work with lineages in multiple parents hierarchies effectively, because it only stores items. To overcome this, HS should have means to store individual lineages, instead of individual items. Because it's not very common feature, it seems logical to put in API so it only affects those HS implementation that need it.
#1
HS is just a widget and does not and should not and will not provide data storage itself. I'm sticking with that. If you want to have the ability to remember lineages with multiple parents (as you explained clearly in follow-up #4 of #476656), then it is up to the underlying module to support that. IMO, it should be considered a bug in Taxonomy, not a bug in HS, that this is impossible.
#2
I understand that you want to clear issue queue, but atleast try to read carefully :)
I didn't mean that HS should store it itself, it's reasonable that HS provides widget and widget only. However, once there is module supporting storing lineages, HS will need modification too, since HS will still calculate lineage old way and get wrong results displayed in dropbox. So this problem can't be solved purely outside of HS. That's why I suggested to change API so HS atleast would become aware of the actual lineage, so HS wouldn't calculate lineage but get provided lineage out of storage (while storage module would be provided outside of HS as part of HS API implementation).
#3
Oh, sorry, I didn't understand you that way — I had not even thought of that!
But you're absolutely right, of course. Thanks for insisting :)
This should be implemented in the next major version of HS.