Query Array Not Choosing the last choice

[kjaymiller]

When I have a query array, the last option generates no matching section found in <.

---
title: Testing Query Arrays
---

snippet = ?[jay, foo, bar, biz]

<<#${snippet}
___
#[jay]
* say "jay"

#[foo]
* say "foo"

#[bar]
* say "bar"

#[biz]
* say "biz"

/*
Returned from Log
2021-04-09 13:07:55: ⚪[nova] Open >>>>>>>>>>>>>>>>>>>>>
2021-04-09 13:07:55: ⚪Presenting multiple choice from array: (
jay,
foo,
bar,
biz
)
2021-04-09 13:07:58: ⚪Multiple Choice answered (biz)
2021-04-09 13:07:58: 🔴[nova] Specified snippet fragment "#${snippet}", no matching section found in <.
2021-04-09 13:07:58: 🔘Generating status menu
2021-04-09 13:07:58: ⚪[nova] Launching app (snippet = ?[jay, foo, bar, biz])
*/

[ttscoff]

With beta 86? Just tested with the above Bunch and got all 4 options to work.

[kjaymiller]

Still having the same issue. Also FWIW. I restarted the application and updated to Version 1.4.0 (86)

[ttscoff]

With the exact Bunch you posted here? Because that's working without a hitch for me. Are you testing it with other elements that could be affecting it?

…

On 9 Apr 2021, at 15:39, Jay Miller wrote: Still having the same issue. Also FWIW. I restarted the application and updated to Version 1.4.0 (86) -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #51 (comment)

[kjaymiller]

It's related to another issue where bunch is not crashing but not running. When I quit and reload bunch it corrects the issue and runs. Not sure if this is a caching issue but my assumption it is because I'm making a lot of changes to bunches at the moment.

[ttscoff]

Bunch should take less than a second to reload after it detects changes, so frequent changes shouldn't really cause issues (I change and toggle bunches in very fast succession when testing changes).

I'd be curious to see whatever you can share from the affected Bunch, it might help me track down issues.

[kjaymiller]

I think at this point the problem is resolved. If I can recreate the issue, I'll definitely share any information.