case EntityTypeName::kOrder:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";
case EntityTypeName::kShipment:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";Victor ShuIs this read only status decided or should this rather be a NOTIMPLEMENTED()?
Same in some of the other files.
I followed the FlightReservation entity implementation and Order and Shipment seem similar in nature to be read only.
// Shipments are read-only and do not use attribute strings.Victor ShuWhy do we define strings in autofill_strings.grdp then?
removed from autofill_strings.grdp
SHIPMENT_ASSOCIATED_ORDER_ID = 215,Victor ShuWhat is the associated order ID? Is this the value of the ORDER_ID or is it the guid() of the associated order entity?
should match with the ORDER_ID.
case EntityTypeName::kShipment:Victor ShuHas it been decided which preferences will control order and shipment?
Not sure about this
return Suggestion::Icon::kNoIcon;Victor ShuShould this rather be a NOTIMPLEMENTED()?
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
case EntityTypeName::kOrder:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";
case EntityTypeName::kShipment:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";Victor ShuIs this read only status decided or should this rather be a NOTIMPLEMENTED()?
Same in some of the other files.
I followed the FlightReservation entity implementation and Order and Shipment seem similar in nature to be read only.
Yes, but for flight reservations, product has actually decided that the should be read-only in Chrome.
I think until we know, this should just be `NOTIMPLEMENTED()`
// Shipments are read-only and do not use attribute strings.Victor ShuWhy do we define strings in autofill_strings.grdp then?
removed from autofill_strings.grdp
We are still defining some strings? Is this necessary/recommended (I genuinely don't know. Perhaps the entitiy names are necessary to display them in settings somehow)?
SHIPMENT_ASSOCIATED_ORDER_ID = 215,Victor ShuWhat is the associated order ID? Is this the value of the ORDER_ID or is it the guid() of the associated order entity?
should match with the ORDER_ID.
Please add a comment then describing this relation.
case EntityTypeName::kShipment:Victor ShuHas it been decided which preferences will control order and shipment?
Not sure about this
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
case EntityTypeName::kOrder:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";
case EntityTypeName::kShipment:
NOTREACHED() << "Entity is read only and doesn't support save prompts.";Victor ShuIs this read only status decided or should this rather be a NOTIMPLEMENTED()?
Same in some of the other files.
Florian LeimgruberI followed the FlightReservation entity implementation and Order and Shipment seem similar in nature to be read only.
Yes, but for flight reservations, product has actually decided that the should be read-only in Chrome.
I think until we know, this should just be `NOTIMPLEMENTED()`
looks like product decided both Order and Shipment are read only.
// Shipments are read-only and do not use attribute strings.Victor ShuWhy do we define strings in autofill_strings.grdp then?
Florian Leimgruberremoved from autofill_strings.grdp
We are still defining some strings? Is this necessary/recommended (I genuinely don't know. Perhaps the entitiy names are necessary to display them in settings somehow)?
Yes, i think it's recommended. Also, following the pattern from other entity cls.
SHIPMENT_ASSOCIATED_ORDER_ID = 215,Victor ShuWhat is the associated order ID? Is this the value of the ORDER_ID or is it the guid() of the associated order entity?
Florian Leimgrubershould match with the ORDER_ID.
Please add a comment then describing this relation.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |