Closed theijhay closed 1 month ago
We are not using external services. Also I do not agree with calling a content api for every single piece of content. Frontend usually have translation files, this is a better way of supporting multi-lingual than what is described here
We are not using external services. Also I do not agree with calling a content api for every single piece of content. Frontend usually have translation files, this is a better way of supporting multi-lingual than what is described here
It has been adjusted sir.
Description
Acceptance Criteria
Purpose
Requirements
1. Develop Backend API Endpoints:
2. Implement Caching Mechanisms:
3. Ensure Data Security and Compliance:
Expected Outcome
1. Localized Content Delivery:
2. Improved Performance:
3. Data Security Compliance:
4. Scalability:
5. Reliability:
Endpoint Results
1. GET /api/v1/translations/{language}
2.POST /api/v1/translations
3. DELETE /api/v1/translations/{language}
4. GET /api/v1/languages
Tasks
GET
,POST
,DELETE
endpoints).Testing
1. Verify Valid Language Codes Return Expected Content:
GET
request with a known valid language code (e.g., "en").2. Check Handling of Invalid Language Codes:
GET
request with an invalid language code (e.g., "xyz").3. Verify Content Update Functionality:
POST
request with new content for a valid language code.4. Ensure Content Validation on Update:
POST
request with invalid content data (e.g., missing required fields).5. Verify Deletion of Content:
DELETE
request for a specific language code.6. Verify Caching Functionality for Language-Specific Content Retrieval:
7. Ensure Caching Expiration and Refresh Mechanism:
Technical Skills Required
Relevant Categories
Backend Development
API Integration
Multilingual Support
Mentor