Repository navigation
feat(lumabot): plugin rank (!rank, !rank global) - #372
Merged
Merged
Conversation
Serviço rank (record/top) com contagem por chat e total global. Nada chama record até o plugin ai existir; item do PARIDADE segue desmarcado. Closes #344
record serializado no processo, doc dos limites e do escopo de sessão, ranking enviado sem citar a mensagem como no legacy.
# Conflicts: # apps/lumabot/docs/README.md # apps/lumabot/src/main.ts
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
1 participant
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.
O que muda
rankcomrecord(chatId, senderId)etop(scope, limit). Usa duas coleções, por chat e global, e orecordprocessa uma chamada de cada vez.!ranke!rank global(na DM, sempre global) saem sem citar a mensagem, como no legacy. Os nomes vêm douserNamesquando ele está ligado.recordainda. No legacy, só a IA contava interações, então oaido M5 vai alimentar o ranking. Por isso o item doPARIDADE.mdsegue desmarcado.Collectiondo Bridger não tem incremento atômico.Empilhado: depende do #368 e do PR do
user-names.Verificação
pnpm lint,typecheckebuildpassam. Empnpm test, só falham 2 testes:!gifem MP4 e!stickerde vídeo em 800 KB. Os dois já falham nodevelop, por causa do ffmpeg 8.1 do ambiente.Closes #344