feat: ability to view tasks in a category #19
@ -1,3 +1,4 @@
|
||||
use std::hash::Hash;
|
||||
use crate::schema::tasks;
|
||||
use chrono::{Duration, NaiveDate, NaiveTime};
|
||||
use diesel::deserialize::FromSql;
|
||||
@ -11,7 +12,7 @@ use serde_with::DurationSeconds;
|
||||
use std::io::Write;
|
||||
|
||||
#[serde_with::serde_as]
|
||||
#[derive(AsExpression, FromSqlRow, Serialize, Deserialize, Hash, Clone, Debug)]
|
||||
#[derive(AsExpression, FromSqlRow, Serialize, Deserialize, Clone, Debug)]
|
||||
#[diesel(sql_type = Jsonb)]
|
||||
pub enum Category {
|
||||
Inbox,
|
||||
@ -45,6 +46,12 @@ impl Category {
|
||||
}
|
||||
}
|
||||
|
||||
impl Hash for Category {
|
||||
fn hash<H: std::hash::Hasher>(&self, state: &mut H) {
|
||||
std::mem::discriminant(self).hash(state);
|
||||
}
|
||||
}
|
||||
|
||||
impl PartialEq for Category {
|
||||
fn eq(&self, other: &Self) -> bool {
|
||||
std::mem::discriminant(self) == std::mem::discriminant(other)
|
||||
|
||||
@ -13,7 +13,7 @@ pub(crate) fn use_tasks_in_category_query(category: Category)
|
||||
|
|
||||
|
||||
async fn fetch_tasks_in_category(keys: Vec<QueryKey>) -> QueryResult<QueryValue, QueryErrors> {
|
||||
if let Some(QueryKey::TasksInCategory(category)) = keys.first() {
|
||||
match get_tasks_in_category(category.clone()).await {
|
||||
Consider improving error handling in The use of Suggested changes to improve error handling: And for the unexpected keys: **Consider improving error handling in `fetch_tasks_in_category`.**
The use of `panic!` for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.
Suggested changes to improve error handling:
```rust
Err(error) => {
log::error!("Unexpected error: {:?}", error);
Err(QueryErrors::UnexpectedError)
}
```
And for the unexpected keys:
```rust
else {
log::warn!("Unexpected query keys: {:?}", keys);
Err(QueryErrors::InvalidQuery)
}
```
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
match get_tasks_in_category(category.clone()).await {
|
||||
|
Consider improving error handling in The use of Suggested changes to improve error handling: And for the unexpected keys: **Consider improving error handling in `fetch_tasks_in_category`.**
The use of `panic!` for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.
Suggested changes to improve error handling:
```rust
Err(error) => {
log::error!("Unexpected error: {:?}", error);
Err(QueryErrors::UnexpectedError)
}
```
And for the unexpected keys:
```rust
else {
log::warn!("Unexpected query keys: {:?}", keys);
Err(QueryErrors::InvalidQuery)
}
```
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
Ok(tasks) => Ok(QueryValue::Tasks(tasks)),
|
||||
Err(ServerFnError::WrappedServerError(errors)) => Err(QueryErrors::Error(errors)),
|
||||
Err(error) => panic!("Unexpected error: {:?}", error)
|
||||
|
||||
|
Consider improving error handling in The use of Suggested changes to improve error handling: And for the unexpected keys: **Consider improving error handling in `fetch_tasks_in_category`.**
The use of `panic!` for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.
Suggested changes to improve error handling:
```rust
Err(error) => {
log::error!("Unexpected error: {:?}", error);
Err(QueryErrors::UnexpectedError)
}
```
And for the unexpected keys:
```rust
else {
log::warn!("Unexpected query keys: {:?}", keys);
Err(QueryErrors::InvalidQuery)
}
```
<!-- This is an auto-generated comment by CodeRabbit -->
Consider improving error handling in The use of Suggested changes to improve error handling: And for the unexpected keys: **Consider improving error handling in `fetch_tasks_in_category`.**
The use of `panic!` for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.
Suggested changes to improve error handling:
```rust
Err(error) => {
log::error!("Unexpected error: {:?}", error);
Err(QueryErrors::UnexpectedError)
}
```
And for the unexpected keys:
```rust
else {
log::warn!("Unexpected query keys: {:?}", keys);
Err(QueryErrors::InvalidQuery)
}
```
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
Consider improving error handling in
fetch_tasks_in_category.The use of
panic!for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.Suggested changes to improve error handling:
And for the unexpected keys:
Consider improving error handling in
fetch_tasks_in_category.The use of
panic!for handling unexpected errors (lines 19 and 22) is risky in a production environment as it can cause the application to crash. Consider logging these errors or returning a controlled error response instead.Suggested changes to improve error handling:
And for the unexpected keys: