Tom Rhys Jones
Tom Rhys Jones
Ah yeah, totally. If we're committed to doing that, then let's go for it. Minimally, it shouldn't get stuck like it is now though in the current imp.
Yeah, I think ideally we would handle this in a way that still creates a partial transaction that the member can edit the waypoints to fix it - @neil-marcellini references...
Hm, why wouldn't we show the category violation right away if categories are required on the workspace? 🤔 CC: @JmillsExpensify @cead22
Yeah, I agree with it insofar as I don't know why it's disappearing. This is violations related though, so one for #wave-control. :)
>I think I also agree with @trjExpensify that the violation should be shown as long as it's required by the workspace, regardless of whether it's scanning or not. @cead22 Do...
Is something taking this on internally? Is it part of the fire clean-up or something?
@rojiphil any feedback on [this](https://github.com/Expensify/App/issues/40767#issuecomment-2091230417)?
>I think we discussed before if we should even allow the deeplink once user completed the flow @trjExpensify I don't recall that, but it kinda' makes sense. If they've completed...
Looks like we're ready for a re-review here, @c3024. Thanks!
I agree the infinite loading spinner isn't great, but I think this is a [dupe](https://github.com/Expensify/App/issues/13826) and been around for a long time. The real solution for this is better support...