feat: implement achievement service #121
Open
Conversation
This file contains hidden or 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
… transaction modules - Add AppModule to initialize the application with necessary modules. - Create Energy module for managing user energy regeneration, consumption, and status. - Implement Shop module for handling shop items, including creation, retrieval, and purchasing. - Develop Transaction module for processing user transactions, including purchases and refunds. - Introduce Payment module to manage payment processing with providers like Stripe and PayPal. - Add necessary entities, controllers, and services for each module. - Implement cron job for periodic energy regeneration. - Set up TypeORM for PostgreSQL database integration. - Configure global validation and CORS in the main application bootstrap.
…the achievement microservice
fawizzy
changed the title
Contributor
|
@fawizzy please resolve conflict |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR adds a new
achievement-serviceNestJS microservice responsible for defining, tracking, and unlocking player achievements, as well as awarding badges. The service runs independently with its own Postgres database and exposes APIs for querying achievement definitions, user progress, and unlock history.Key Changes
New Microservice:
microservices/achievement-serviceeconomy-service)quest_achievement)Dockerfileanddocker-compose.ymlDomain Entities
Achievement: definition (code, metric, targetValue, rarity, etc.)AchievementProgress: per-user progress (unique per user + achievement)Badge: awarded badge per unlocked achievement (idempotent)Core Services
AchievementService: manage achievement definitionsAchievementProgressService: record and fetch user progressAchievementUnlockService: evaluate unlocks and orchestrate side effectsBadgeService: award and query user badgesAchievementHistoryService: fetch user unlock historyAchievementNotificationService: unlock hook (currently logs)Core Logic
HTTP API
GET /achievements– list all achievement definitionsGET /users/:userId/achievements– get user progressGET /users/:userId/achievement-history– get unlock historycloses #103