The encrichments should be quite self-contained, this will certainly be required for if we eventually wish to support DI of enrichments.
There is currently enrichment related functionality in toggle-injector. The core G-S code should start by selecting a block of cells (according to whether it's a row or column enrichment) - then sort out what type of enrichment it is, and pass the cells to the enrichment.
Well, since heatmap will affect the cells themselves, I guess the standard APi for an enrichment should include:
- operateOn(cellStrings, cells, table, isRow)
- name
- description
- canOperateOnNumeric
- canOperateOnCategorical
Once all enrichments match this API, G-S itself will know much less about them.
We should probably add a section to the G-S readme about how to create a new enrichment.
The encrichments should be quite self-contained, this will certainly be required for if we eventually wish to support DI of enrichments.
There is currently enrichment related functionality in
toggle-injector. The core G-S code should start by selecting a block of cells (according to whether it's a row or column enrichment) - then sort out what type of enrichment it is, and pass the cells to the enrichment.Well, since
heatmapwill affect the cells themselves, I guess the standard APi for an enrichment should include:Once all enrichments match this API, G-S itself will know much less about them.
We should probably add a section to the G-S
readmeabout how to create a new enrichment.