Learn how to use Dash Bio for next-gen sequencing & quality control. 🧬Register for the Oct 27 webinar.

Differences in structure of IDs from MATCH pattern and ALL pattern

I noticed that the structure of ID data received is different in ALL pattern vs MATCH pattern.
Hope it helps someone to know it before hand. I have spent quite some time to figure this out as it was not working as expected.

MATCH vs ALL pattern:

  • List item

ALL:The IDs are in a list form. A list of ID where each ID is a dictionary
```
[{‘type’: ‘table-display’, ‘index’: 0}, {‘type’: ‘table-display’, ‘index’: 1}]

MATCH:The ID is coming in the call-bak automatic loop with only one ID dictionary at a time. Example from 2 auto-loops below.

{‘type’: ‘table-display’, ‘index’: 1}
{‘type’: ‘table-display’, ‘index’: 0}


ALL:As you can see sample data above, the order IDs based on their indices is ascending
MATCH: The order is descending. Ideally the expectation is ascending so the looping is easy. But I guess DASH automatically matches it may not matter though.

Not sure if its something by design and intentional. But, the not sure why individual item in MATCH and a list in ALL. In my opinion, it should be in same format so from coding perspective for call back functions, we don't have to handle separately.