Integrate nillion frontend #3391
Open
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
Client running correctly Character file for vsa agent Action for gathering userData (placeholder data upload)
Added basic storage and data retrieval with nillion, fixed issues that were preventing correct building
Dataformat currently a placeholder but upload and retrieval functioning using user id
Nillion folder is now correctly setup in the repository and the functions can be called by the agent
Nillion functionality
- Set up Next.js with TypeScript and TailwindCSS - Add basic app structure and configuration - Configure development environment - Add initial homepage layout
Feat/frontend setup
- Add hero section with VSA introduction - Create features grid highlighting VSA, smart contracts, and Telegram integration - Add CTA section for agent deployment - Update design system with dark theme and gradients - Implement Space Grotesk font
- Create comprehensive TypeScript interfaces for bounties and VSAs - Implement singleton-pattern API services with proper error handling - Add mock data for development - Create detailed documentation This commit sets up the foundation for frontend-backend communication while allowing independent frontend development using mock data. Key additions: - Type definitions for all data structures - Service layer with proper error handling - Mock data matching production structure - Detailed README with best practices
feat(landing): create LFG platform landing page
Feat/api integration setup
- Create bounty board page with grid layout and consistent spacing - Add shared navigation component for consistent header across pages - Update root layout to use shared navigation - Fix path aliases in tsconfig.json - Style bounty cards with gradient accents - Maintain consistent design language with landing page The bounty board now matches the landing page's design while providing a clear overview of available opportunities.
- Add proper Tailwind configuration - Create reusable component classes for navbar elements - Organize global styles into proper layers - Fix CSS syntax issues - Add consistent styling for buttons and links
feat(frontend): implement bounty board UI
- Add dashboard layout with navigation sidebar - Create overview page with stats and activity feed - Match site's color palette and design system - Add VSA status indicator
feat(dashboard): implement modern dashboard UI
Added + tested functions for creating and adding bounties tied to a user id to the nillion storage. Added updated Nexus character file
Creating and Retrieving Bounties
- Add bounties list with filtering (all/active/applied/completed) - Create bounty cards with status badges and skill tags - Implement rating system for completed bounties - Add applied status for pending applications
- Add VSA profile configuration page with status, skills, and preferences - Fix logo alignment across all pages - Update layout structure for better consistency - Match main site's color scheme
- Add CreateBountyModal component with form fields and wallet integration - Add click-outside to close functionality - Connect modal to main bounties page and dashboard - Make button text and styling consistent - Remove duplicate button from dashboard bounties page
feat(dashboard): implement bounties tab page
- Add bounty detail page with back navigation - Update CreateBountyModal to match Bounty type - Ensure data consistency across components - Add completion criteria and repository URL fields - Fix IconBrandGithub import
feat: add bounty detail page and fix data consistency
Fixed the nillion storage for bounties added functions for creating and retrieving bounties Added actions for creating and getting Bounties
Task storage
- Add feature flags configuration - Create useFeature hook and FeatureGate component - Update components to use feature flags - Add Vercel configuration - Update bounty components with feature-gated functionality
- Add pnpm workspace and npmrc configuration - Fix type errors in CreateBountyModal - Update services to properly handle query params - Add package manager and engine requirements
- Install nillion-sv-wrappers package - Update client initialization - Update API methods to match SDK
- Update client initialization to use proper SDK methods - Fix collection and data retrieval methods - Update data update method
- Update client initialization to match SDK requirements - Update collection and data methods to match SDK - Add more detailed logging
- Update client to use schema ID in constructor - Update API to use readFromNodes and updateDataToNodes - Remove collection creation step
- Downgrade nillion-sv-wrappers to 1.0.4 - Update client initialization to match original implementation - Remove schema ID from constructor
- Add getCollection method to client - Update API to use collection-specific operations - Fix initialization order
- Make getCollection public - Add Bounty type definition - Transform bounties to match expected format - Add default values for missing fields
- Remove unnecessary client initialization in getCollection - Match original implementation more closely
- Add detailed logging in client getCollection - Add detailed logging in API for bounty fetching - Log data types and full JSON structures
- Match original implementation's data handling - Use flatMap to handle nested bounties array - Add better error handling for undefined values
User Data storage and Bounty Data storage now provide functions for creating and retrieving Actions for creating user/bounty fully functional
- Add test bounty creation on first read - Handle empty collection case - Add more detailed logging
- Add schema.json for bounty collection - Add schema initialization to client - Make schema IDs mutable - Try to initialize schema before fetching bounties
- Update schema.json to use format - Update test bounty to use format - Update data transformation to handle fields
- Initialize collection before creating schema - Use schema.default for imported JSON - Add better error handling and logging - Only update schema ID if valid
- Use getBountyList from @/nillion directly - Remove schema initialization - Remove collection management - Keep same return format for compatibility
Feat/nillion bounty integration
User can now request to see bounties that match his skills
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
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.
Relates to
Risks
Background
What does this PR do?
What kind of change is this?
Documentation changes needed?
Testing
Where should a reviewer start?
Detailed testing steps