Wagering #19
Open
Wagering #19
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
|
@fmhall is attempting to deploy a commit to the Merit Systems Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rsproule
reviewed
Dec 8, 2025
| wagerId: string, | ||
| winningSide: string, | ||
| proofUrl?: string, | ||
| ): Promise<WagerWithPositions> { |
Collaborator
There was a problem hiding this comment.
can anyone in the group just resolve at any time to their side?
Author
There was a problem hiding this comment.
Basically, but proof requirements are determined by the bot. I want to give it a web search tool in addition to it's photo analysis tool.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
All code uses the abstractions previously created. Currently did not create a seperate personality, but can do that later.
Disabled by default unless the
wageringEnabledflag is set to true in group chat settings.Tried to go for a minimal diff, follow best practices, no slop.
Goal is to support this kind of flow:
Mostly all implemented, without testing though.
Only thing missing is that no proactive hook exists - so people would have to prompt it to resolve wagers.