Closed Harman-singh-waraich closed 8 months ago
Name | Link |
---|---|
Latest commit | 1e4d3b25efa9187027b3dc3c0f8a54cbeb82e7e0 |
Latest deploy log | https://app.netlify.com/sites/curate-v2/deploys/65fcd7b11aed8e0008a6cff4 |
Deploy Preview | https://deploy-preview-18--curate-v2.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Rationale
_listMetadata
(ipfs url eg. "/ipfs/QmPug3tLWPE1SRDkBu9kiZZwAVRhEfZ1RMT17sFiKBhaZn/list.json") inNewList
(previouslyNewGTCR
) event, which is then stored in subgraph. Making it simpler to fetch this data in Frontend.ipfs
orsubgraph
actionWhy
listMetadata
as ipfs url ?Note :
_listMetadata
argument todeploy
function inCurateFactory
,Stack too deep
error was being faced._templateRegistry_
, registrationTemplateParameters,_removalTemplateParameters_
as a StructTemplateRegistryParams
⚠️ This will make list metadata immutable as it is set at list deploy time , previously we could change it through updating dispute template. Do we want this behaviour?
PR-Codex overview
The PR enhances Curate contracts, subgraph, and React app by updating dependencies, metadata, and event names.
Detailed summary