...
After a conversation with Pawel, we discovered that we can control this through Sanity, where we can add these rules to the restaurant document within Sanity and retrieve/modify this file in other services such as DOP.
Detailed solutions
ctg-fz-portal
#We Prefer this Solution
After a conversation with Pawel and Francisco, we resolved to create the Sanity-client Lib into the DOP service, this way is simpler and resolve our problem. Only DOP there are access to change this information, so we don’t have problems in this are into only DOP.
Zenuml sequence macro lite | ||||||
---|---|---|---|---|---|---|
| ||||||
Create a query to add new data of cash limitation in the sanity through DOP
Add new data of rules of Cash Limitation in restaurant interface;
Add this rules of cash limitation in the DOP service;
Import the sanity-client in DOP
Intl-packages
#We Prefer this Solution
To do this, we simply need to add the data control logic in intl-packages/package/sanity and import this package into DOP. This allows us to centralize restaurant information in just one place (Sanity), making the implementation simpler.
Zenuml sequence macro lite | ||||||
---|---|---|---|---|---|---|
|
Detailed solutions
1. Intl-packages
...
| |
Create all the logic for adding, updating, and removing cash limitation rules in the packages on Sanity Package;
Add new data of rules of Cash Limitation in restaurant interface;
Add this rules of cash limitation in the restaurant.tsx file on intl-whitelabel-cms repository;
Import the
intl-packages/sanity
in DOP repository, and the DOP uses these function to persist on Sanity
...
Place all this control in
intl-package/package/restaurant
and import this package into DOPAdd this control to
intl-store-service
and create an SDK for this service in DOP
1. Intl-packages
#We prefer this solutionWe prefer this option because it is faster and simple in the development, and the query of list of restaurants is in this repository.
...