Repository navigation
feat(prices): add price alerts with target price and history trend - #4
Merged
Merged
Conversation
Conflito só em backend/app/main.py (import e rotas novas no fim do arquivo): mantidas as duas partes.
This was referenced Nov 18, 2026
Collaborator
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
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.
Summary
Price alerts: the user sets a target price per part, and the status combines the current price search with the stored history.
POST /alertascreates an alert (part + target price) for a user.GET /alertaslists each alert with the cheapest current offer and its source, the historical low and the trend.backend/app/alertas.py, built onprecos.pesquisarandprecos.historico, so it works with both the seed and the Serper provider.Related to #1.
Notes
Test plan
cd backend && uv run pytest(85 passed, includingtests/test_alertas.py)