device infos
This commit is contained in:
@@ -572,10 +572,12 @@ Future<ServiceProfile> resolveServiceProfile() async {
|
||||
// patterns collide. Tenant 13 carrying a display name that normalises to
|
||||
// `doormile` — which is, after all, the company that owns the tenant record —
|
||||
// resolved that rider to Logistics and never consulted the id at all. On the
|
||||
// Logistics line `_unreleased` is empty by design, so the **Start round** bar
|
||||
// does not render, and once `MILER_COLLECTED_STATE_ENABLED` is on his
|
||||
// collected parcels strand at `Collected_By_Miler` with no control to release
|
||||
// them. A global flag gets one safe shot, and this was the loose end in it.
|
||||
// Logistics line a rider has no customer round at all — he carries what he
|
||||
// collects to the hub — so nothing in the app will ever call
|
||||
// `start-delivery` for him. Once `MILER_COLLECTED_STATE_ENABLED` is on, a
|
||||
// meal rider resolved onto Logistics has his collected orders strand at
|
||||
// `Collected_By_Miler` with no control anywhere that releases them. A global
|
||||
// flag gets one safe shot, and this was the loose end in it.
|
||||
//
|
||||
// A deliberate statement about a known tenant outranks a match on a word
|
||||
// nobody on either side of the API controls the spelling of.
|
||||
|
||||
Reference in New Issue
Block a user