You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user,
I want the Passport application to only load data from the Scorer backend,
So that no requests for reading data from the Ceramic network are performed.
Acceptance Criteria
GIVEN I am a user of the Passport application,
WHEN I open the Passport application,
THEN the application is only loading data from the Scorer backend (Ceramic cache),
AND no requests for reading data from the Ceramic network are performed.
Product & Design Links:
Tech Details:
The implementation should ensure that data is only being fetched from the Scorer backend and not Ceramic.
Open Questions:
Notes/Assumptions:
This change is part of the migration from Ceramic to ComposeDB. The backfilling of data from Ceramic is no longer necessary.
The text was updated successfully, but these errors were encountered:
erichfi
changed the title
Update the Passport App - drop back-filling data from ceramic
Update Passport App to Load Data Exclusively from Scorer Backend
Aug 3, 2023
User Story:
As a user,
I want the Passport application to only load data from the Scorer backend,
So that no requests for reading data from the Ceramic network are performed.
Acceptance Criteria
GIVEN I am a user of the Passport application,
WHEN I open the Passport application,
THEN the application is only loading data from the Scorer backend (Ceramic cache),
AND no requests for reading data from the Ceramic network are performed.
Product & Design Links:
Tech Details:
The implementation should ensure that data is only being fetched from the Scorer backend and not Ceramic.
Open Questions:
Notes/Assumptions:
This change is part of the migration from Ceramic to ComposeDB. The backfilling of data from Ceramic is no longer necessary.
The text was updated successfully, but these errors were encountered: