-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge to main and deploy to Cloudflare #37
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add missing key prop to Link component in DaoList to prevent React warnings and improve rendering performance - Update wrangler.toml configuration
- Add 'use client' directive to DaoList component to prevent hydration errors - Add empty [vars] section to declare environment variables in wrangler.toml - Remove [env] section from wrangler.toml - Allow variable values to be managed via Cloudflare Dashboard secrets
- Add SSR detection to skip provider when running on server - Prevent context errors during build time when graphKey is empty - Maintain original provider functionality in browser environment - Keep type safety and existing provider interface
- Remove edge runtime directive from DAO page to resolve static generation issues - Add 'use client' directive to ensure DAO hooks run client-side only - Update DaoHooksProvider to handle SSR context gracefully This resolves the build error 'DaoHooksContext must be used within a DaoHooksProvider' during static page generation.
- Keep 'use client' directive for root page - Use dynamic import for DaoList without SSR flag This resolves the 'DaoHooksContext must be used within a DaoHooksProvider' error during static generation.
- Add mounted state to DaoList to prevent SSR hooks - Mark root page as client component to support DaoList context This resolves the DaoHooksContext error during static generation.
- Add force-dynamic export to root page - Keep client component directive - Maintain DaoList client-side rendering This prevents prerender errors with DaoHooksContext during build.
Renames imported dynamic function to avoid collision with Next.js page config export
fix: add key prop to Link component in DaoList
feat: redesign connect view with centered gate
- Move wallet connection and chain name logic to page component - Simplify DaoList to focus on displaying DAOs - Improve styling and layout
refactor: move connection UI from DaoList to page component
adds active prop fetch hook and display in dao list card
- Add Avatar component for DAO images - Style cards - Add truncation for long DAO names (>25 chars)
- Add Avatar component for DAO images - Style cards - Add truncation for long DAO names (>25 chars) - Integrate active proposals count from dev
Display 'Active Proposal' for single proposal and 'Active Proposals' for zero or multiple proposals
- Add loading check for proposals data - Rename loading states (daoLoading, proposalsLoading) - Calculate proposalCount before render - Handle both loading states before component render
- Add font preloading for FetteUNZFraktur - Add text-rendering optimization - Standardize font-face declarations - Reduce Largest Contentful Paint (LCP) time
Daos list
Make proposal and no DAOs view
…o "Make Proposal" across all forms\n- Standardize form label styles using ProposalFormLabel\n- Fix Description placeholder text capitalization\n- Normalize validation messages across all form fields\n- Update validation message styling to use destructive color\n- Clean up form field spacing and layout\n- Remove unused SampleForm component
Tweaking hard on proposals
removes the throw
moves some styles
- Hide form fields after confirmation - Add heart SVG image to success state
✅ Deploy Preview for celadon-stardust-69bc7a ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.