wip: require exact match of data field segments for automations

[jessicamcinchak]

An experiment!

Comes out of planning constraints testing: with current automations behavior, listed.grade.II incorrectly auto-answers listed.grade.I because each segment uses a "startsWith" match rather than exact.

This one-line change now does what we want in this specific use case, but services team will have to determine if it unexpectedly breaks other areas of the schema !

More context here from August https://opensystemslab.slack.com/archives/C04DZ1NBUMR/p1721902632687949?thread_ts=1721219483.725279&cid=C04DZ1NBUMR

The way values match is matching-up-to, the . separator isn't material to that behaviour. value.valueAndThenSome matches to value.value or value.valueAnd etc. the same way that value.value.AndThenSome matches to value.value. So changing to listed.gradeI and listed.gradeII wouldn't change that behaviour, the former would still match to the latter. Counterintuitive to our use of . separators and something to be changed perhaps?

[github-actions]

Pizza

Deployed 062d7f9 to https://3461.planx.pizza.

Useful links:

• Editor
• Storybook
• Hasura
• API
• ShareDB