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
The story details and condition details are currently stored together in one blob but only the manager, researcher, and evaluator are able to see the condition details so it doesn't make sense to retrieve the condition details every time the story is viewed.
Acceptance Criteria:
Condition details content is stored separately from the story details
Condition details are fetched from IPFS once they are requested to be viewed
May be able to use IPFS DAG instead which wouldn't require any refactoring of the storage format, only a change to the impl being used to save the data and accessing only the necessary objects.
Can't be implemented with IPFS DAG until colonyJS accepts CID formatted specification hashes
The text was updated successfully, but these errors were encountered:
The story details and condition details are currently stored together in one blob but only the manager, researcher, and evaluator are able to see the condition details so it doesn't make sense to retrieve the condition details every time the story is viewed.
Acceptance Criteria:
May be able to use IPFS DAG instead which wouldn't require any refactoring of the storage format, only a change to the impl being used to save the data and accessing only the necessary objects.
Can't be implemented with IPFS DAG until colonyJS accepts CID formatted specification hashes
The text was updated successfully, but these errors were encountered: