Ben
What are the action items we're consolidating? To me, there is only one action item that operations cares about - receipts. The only other action item I can think of...
Any card details fields should be in an iFrame so they can't be accessed by the host origin, no?
Blocking on a plan being made around a new application flow.
~~Note to self: use `x-cloak`~~
@cjdenio would like your input here What magical concoction of `x-effect` and co. would be needed to avoid `"x-bind:disabled": "disabled && !JSON.parse(JSON.stringify(managerEvents)).includes(parseInt(sourceEventInput))"` on every single form element?