Efficient way to structure falcor router for deep paths? -

i'm continuing experiments falcor , enjoying of it, i'm noticing concerning.

i'm assembling jsongraph multiple disparate apis, falcor-router intended do. can't seem find way cleanly provide catch-all fields don't need special handling w/o blowing routes do need special handling.

my routes following:

• items[{integers:ids}].name
• items[{integers:ids}][{keys:fields}]

no matter order declare routes in generic 1 wins. there better way avoid full-nuclear option of structuring routes this?

• items[{integers:ids}].name
• items[{integers:ids}]['fooga', 'wooga', 'booga', 'tooga', ... ]

that seems brittle, if data coming backing server changes have update not application code router well. becomes real mess if have nested objects number of permutations climb in hurry.

i believe bug. router should match specific path first. appreciate if log issue. fix you.