engineer-dao / platform

The EngineerDAO dApp for interacting with job contracts
engineer-dao-platform.vercel.app
6 stars 4 forks source link

Adds contract events to activity feed. Closes #123. Closes #41. #135

Closed deweller closed 2 years ago

deweller commented 2 years ago

Use a backend process to sync blockchain events in the background.

Various UI improvements for showing status changes and contract events

All firebase selectors are name-spaced to the current Job contract address

Changes firebase selector for messages and events to jobId/messages and jobId/events

Use environment vars for Firebase

Copy hardhat build artifacts to backend

Adds baseUrl for imports relative to project root

image

Closes #123. Closes #41.

vercel[bot] commented 2 years ago

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

platform – ./frontend

🔍 Inspect: https://vercel.com/engineerdao/platform/2aT4pQ9NLCq3bGpimFJhzUoueZEC
✅ Preview: https://platform-git-feat-123-contract-events-in-act-ee376d-engineerdao.vercel.app

backend – ./backend

🔍 Inspect: https://vercel.com/engineerdao/backend/CCyfUvrk6VDzgyJhhz3s7BL8cK4j
✅ Preview: https://backend-git-feat-123-contract-events-in-acti-eff3aa-engineerdao.vercel.app

deweller commented 2 years ago

There is no programmatic setup for Firebase required. Tables are created dynamically in Firebase.

I think events and messages should remain separate and keyed by ID. (See longer comment in the review response above).

I neglected to add the code to remove outdated blockchain events as part of the sync function. I will do that later as #137.

I will complete the organization tasks.