-
Notifications
You must be signed in to change notification settings - Fork 46
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
Fix: Include quest completion timestamp in get_quest_participants response #359
base: testnet
Are you sure you want to change the base?
Conversation
Hello @TropicalDog17 when will the PR be ready for review ? |
Hey please review this PR. Thank you so much! @Marchand-Nicolas |
@@ -229,8 +229,10 @@ pub fn load() -> Config { | |||
let args: Vec<String> = env::args().collect(); | |||
let config_path = if args.len() <= 1 { | |||
"config.toml" | |||
} else { | |||
} else if (args.len() > 1) && (args.get(1).unwrap().contains("toml")) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As said in the issue, the route we want to update is src/endpoints/admin/quest/get_quest_participants.rs, not src/endpoints/get_quest_participants.rs,
@@ -26,4 +26,8 @@ pub mod tests { | |||
let response = client.get(endpoint).send().await.unwrap(); | |||
assert_eq!(response.status(), StatusCode::OK); | |||
} | |||
|
|||
// #[tokio::test] | |||
// pub async fn test_get_quest_participants() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can remove this
return (StatusCode::OK, Json(res)).into_response(); | ||
(StatusCode::OK, Json(res)).into_response() | ||
} | ||
#[cfg(test)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to have the tests, but it was a good idea to make sure everything was working. The problem is that if we run tests in production, it'll reset the db
Close #358