Repository navigation
refactor: isola dados de domínio por usuário autenticado - #27
Merged
Merged
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
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.
Descrição
Os endpoints autenticados consultavam recursos globais, permitindo acessar e manipular dados de outros usuários. Este PR restringe grupos, terrenos, rações, ocupações e movimentações de estoque ao usuário autenticado. IDs de recursos alheios retornam 404 com o mesmo contrato de recursos inexistentes.
Alterações
Validação
Migration e limites
A migration exige user_id com NOT NULL desde o início. Em ambientes com dados existentes, é necessário definir backfill antes de aplicar a migration.
A consistência de proprietários em Occupation é garantida pelos services. Importações e escritas diretas no banco precisam preservar essa regra.