Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request new match #74

Merged
merged 11 commits into from Oct 22, 2023
Merged

Request new match #74

merged 11 commits into from Oct 22, 2023

Conversation

q-Sci
Copy link
Contributor

@q-Sci q-Sci commented Oct 15, 2023

Fix #42

@q-Sci q-Sci linked an issue Oct 15, 2023 that may be closed by this pull request
@q-Sci q-Sci requested a review from GregTCLTK October 17, 2023 12:36
questions.ts Outdated Show resolved Hide resolved
@GregTCLTK
Copy link
Member

this pr is kinda critical as it probably breaks all other open and future prs due to massive merge conflicts

@johan-t
Copy link
Contributor

johan-t commented Oct 18, 2023

this pr is kinda critical as it probably breaks all other open and future prs due to massive merge conflicts

I agree, I think we should first merge #71 and then merge this one

@johan-t
Copy link
Contributor

johan-t commented Oct 18, 2023

Can we also merge this directly into main?

@q-Sci
Copy link
Contributor Author

q-Sci commented Oct 18, 2023

Can we also merge this directly into main?

Yes we can. But what happened to the concept of the pre-production branch?

@q-Sci q-Sci changed the base branch from development to main October 18, 2023 13:29
@johan-t
Copy link
Contributor

johan-t commented Oct 21, 2023

Can we also merge this directly into main?

Yes we can. But what happened to the concept of the pre-production branch?

As long as this branch is a branch of the development branch it is fine, we just need to remember to merge main into development before starting something new

Copy link
Contributor

@johan-t johan-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General Notes:

  • I am not getting a new match, only the one I have been matched with before, we need to safe the previous match in the db and then just skip them when matching

import findMatchingUser from '../../functions/findMatchingUser';
import conversationStarter from '../../functions/conversationStarter';

export const sendQuestion = async (interaction: any) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we declaring the sendQuestion function and not just importing the old one?

sendQuestion(interaction);
} else {
await interaction.reply({
content: 'Bitte beantworte den Meinungstest vollständig, bevor du mit Anderen gematcht werden kannst! Bitte nutze dazu den Befehl `/test`.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we maybe automatically trigger the test command if the user has not finished the test?

@johan-t
Copy link
Contributor

johan-t commented Oct 21, 2023

Also could you think of a way where we could put a button that starts the /match command to make it easier for users to find this feature?

@GregTCLTK GregTCLTK merged commit 96ade8d into main Oct 22, 2023
1 check failed
@GregTCLTK
Copy link
Member

please don't use feature branches to completely re-structure the entire codebase in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Request new match without having to retake the test
3 participants