Controller de Pesquisa não existe.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start with server/routes/search.js, especially lines 7 and 10, and inspect the existing route and controller structure. Separate vehicle search from the broader search responsibility described in the issue, including a search/veiculos route and an exclusive search controller. Done means the root route no longer handles vehicle-only search and the proposed entity-search structure is in place.
Written by the indexing model from the issue text.
Description
Pesquisa não é uma coisa definida somente a veículo. Pesquisa pode ser de veículo, de outras fornecedores, fornecedores proximos, clientes proximos, varias coisas.
A linha 7 do arquivo ./server/routes/search.js não faz muito sentido, sendo que esta usando um controller de veículos:
// linha 7
const controller = app.controllers.veiculo;
A linha 10 também não faz sentido, sendo que a rota "root" ja busca por veículos, e somente.
// linha 10
router.get('/', controller.search);
O certo seria existir uma rota search/veiculos onde chamaria um método de um controller exclusivo (controller.searchVeiculos() por exemplo) para pesquisa que ofereceria métodos de pesquisa para os mais diversos tipos de entidades da aplicação.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from armand1m/tript-api
-
Método .update() do controller de cliente não respeita SRP (Princípio de Responsabilidade Única)Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in armand1m/tript-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
zmo2s/agent-toolbox#23 ·
-
[Bug]: [MCP/CLI] Bare loopback IP addresses (127.0.0.1:port) and hosts with ports fail to navigate due to erroneous scheme inferencePossibly taken @alok-108 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/playwright#43263 ·
Maintainers usually reply within 1 day
-
bug traffic
Difficulty 2/5 Under an hour Newbie friendliness 74/100