Task storage #3377
Open
Task storage #3377
+11,593
−2,312
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
Added + tested functions for creating and adding bounties tied to a user id to the nillion storage. Added updated Nexus character file
Fixed the nillion storage for bounties added functions for creating and retrieving bounties Added actions for creating and getting Bounties
|
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. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hi @Okulon! Welcome to the elizaOS community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now an elizaOS contributor!
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