How luissflores/test-tecnico works
Project Type and Purpose
• This is a hybrid project containing two distinct parts:
a. A set of standalone JavaScript exercises under logico-matematico (logical-mathematical problems).
b. A full-stack “practicos” test implementation:
• A Node.js/Express backend providing a simple Tasks CRUD API.
• A Nuxt (Vue) frontend consuming that API to display and edit tasks.
File Structure Analysis
• Top level:
• logico-matematico/ – JS exercise scripts (ejercicio_*.js).
• practicos/ – practical test: subdivided into backend/ and frontend/.
• practicos/backend:
• index.js – entry point, likely sets up Express app.
• controllers/task.controller.js – business logic for tasks.
• models/tasks.model.js – Task schema or data-access layer.
• routes/task.routes.js & routes/index.js – HTTP route definitions.
• middleware.js – custom Express middleware (e.g., logging or auth).
• .env – environment variables (DB_URI, PORT, etc.).
• practicos/frontend:
• nuxt.config.ts – Nuxt configuration.
• pages/ – page components (index.vue, new.vue, edit.vue).
• components/taskCard.vue – UI card for single task.
• composables/userTask.ts & stores/tasks.ts – Composition API hooks and Pinia store.
• public/ – static assets.
• No explicit database folder, so model likely uses an external service (e.g., MongoDB via Mongoose in .env).
README Insights
• Confirms two exercise sets (logic/math vs. full-stack).
• Practicos frontend wasn’t fully finished due to time.
• .env is present for ease of use.