feat: ability to view tasks in a category #19
| @@ -1,10 +1,8 @@ | ||||
| use crate::models::category::Category; | ||||
| use crate::server::tasks::get_tasks_in_category; | ||||
| use chrono::NaiveDate; | ||||
| use dioxus::core_macro::rsx; | ||||
| use dioxus::dioxus_core::Element; | ||||
| use dioxus::prelude::*; | ||||
| use std::fmt::format; | ||||
|  | ||||
| #[component] | ||||
| pub(crate) fn CategoryInput(selected_category: Signal<Category>, class: Option<&'static str>) -> Element { | ||||
|   | ||||
| @@ -1,7 +1,4 @@ | ||||
| use dioxus::prelude::*; | ||||
| use crate::components::task_list::TaskList; | ||||
| use crate::models::category::Category; | ||||
| use crate::route::Route; | ||||
|  | ||||
| #[component] | ||||
| pub(crate) fn CreateButton(creating: Signal<bool>) -> Element { | ||||
|   | ||||
| @@ -1,6 +1,4 @@ | ||||
| use crate::components::navigation_item::NavigationItem; | ||||
| use crate::components::task_list::TaskList; | ||||
| use crate::models::category::Category; | ||||
| use crate::route::Route; | ||||
| use dioxus::prelude::*; | ||||
|  | ||||
|   | ||||
| @@ -1,6 +1,4 @@ | ||||
|  | ||||
| use dioxus::prelude::*; | ||||
| use crate::components::task_list::TaskList; | ||||
|   Review of imports and module usage. The imports are well-organized and relevant to the component's functionality: 
 Consider removing unused imports to keep the code clean and efficient. **Review of imports and module usage.**
The imports are well-organized and relevant to the component's functionality:
- `dioxus::prelude::*` for Dioxus core functionalities.
- `crate::components::task_list::TaskList` seems unused in this file and could be removed unless it's intended for future use.
- `crate::models::category::Category` and `crate::route::Route` are essential for handling routing and category data.
Consider removing unused imports to keep the code clean and efficient.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| use crate::models::category::Category; | ||||
|   Review of imports and module usage. The imports are well-organized and relevant to the component's functionality: 
 Consider removing unused imports to keep the code clean and efficient. **Review of imports and module usage.**
The imports are well-organized and relevant to the component's functionality:
- `dioxus::prelude::*` for Dioxus core functionalities.
- `crate::components::task_list::TaskList` seems unused in this file and could be removed unless it's intended for future use.
- `crate::models::category::Category` and `crate::route::Route` are essential for handling routing and category data.
Consider removing unused imports to keep the code clean and efficient.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| use crate::route::Route; | ||||
|  | ||||
| #[component] | ||||
|   | ||||
|   Review of imports and module usage. The imports are well-organized and relevant to the component's functionality: 
 Consider removing unused imports to keep the code clean and efficient. **Review of imports and module usage.**
The imports are well-organized and relevant to the component's functionality:
- `dioxus::prelude::*` for Dioxus core functionalities.
- `crate::components::task_list::TaskList` seems unused in this file and could be removed unless it's intended for future use.
- `crate::models::category::Category` and `crate::route::Route` are essential for handling routing and category data.
Consider removing unused imports to keep the code clean and efficient.
<!-- This is an auto-generated comment by CodeRabbit -->   Review of imports and module usage. The imports are well-organized and relevant to the component's functionality: 
 Consider removing unused imports to keep the code clean and efficient. **Review of imports and module usage.**
The imports are well-organized and relevant to the component's functionality:
- `dioxus::prelude::*` for Dioxus core functionalities.
- `crate::components::task_list::TaskList` seems unused in this file and could be removed unless it's intended for future use.
- `crate::models::category::Category` and `crate::route::Route` are essential for handling routing and category data.
Consider removing unused imports to keep the code clean and efficient.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| @@ -1,7 +1,4 @@ | ||||
|   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit -->   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| use dioxus::prelude::*; | ||||
| use crate::components::task_list::TaskList; | ||||
|   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| use crate::models::category::Category; | ||||
|   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| use crate::route::Route; | ||||
|   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
|  | ||||
| #[component] | ||||
| pub(crate) fn NotFoundPage(route: Vec<String>) -> Element { | ||||
|   | ||||
|   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit -->   Consider removing unused imports. The imports  **Consider removing unused imports.**
The imports `TaskList`, `Category`, and `Route` are not used in the current implementation of `NotFoundPage`. If these are not intended for immediate future use, consider removing them to clean up the code.
<!-- This is an auto-generated comment by CodeRabbit --> | ||||
| @@ -1,10 +1,7 @@ | ||||
| use crate::models::category::{Category, Reoccurrence, ReoccurrenceInterval}; | ||||
| use crate::server::tasks::get_tasks_in_category; | ||||
| use chrono::NaiveDate; | ||||
| use crate::models::category::ReoccurrenceInterval; | ||||
| use dioxus::core_macro::rsx; | ||||
| use dioxus::dioxus_core::Element; | ||||
| use dioxus::prelude::*; | ||||
| use std::fmt::format; | ||||
|  | ||||
| #[component] | ||||
| pub(crate) fn ReoccurrenceIntervalInput( | ||||
|   | ||||
| @@ -1,7 +1,4 @@ | ||||
| use dioxus::prelude::*; | ||||
| use crate::components::task_list::TaskList; | ||||
| use crate::models::category::Category; | ||||
| use crate::route::Route; | ||||
|  | ||||
| #[component] | ||||
| pub(crate) fn StickyBottom(children: Element) -> Element { | ||||
|   | ||||
| @@ -1,4 +1,3 @@ | ||||
| use crate::components::home::Home; | ||||
| use crate::components::pages::category_inbox_page::CategoryInboxPage; | ||||
| use crate::components::pages::category_next_steps_page::CategoryNextStepsPage; | ||||
| use crate::components::pages::category_today_page::CategoryTodayPage; | ||||
| @@ -12,7 +11,6 @@ use crate::components::pages::projects_page::ProjectsPage; | ||||
| use crate::components::pages::not_found_page::NotFoundPage; | ||||
| use crate::components::layout::Layout; | ||||
| use dioxus::prelude::*; | ||||
| use crate::models::category::Category; | ||||
|  | ||||
| #[derive(Clone, Routable, Debug, PartialEq)] | ||||
| #[rustfmt::skip] | ||||
|   | ||||
Review of imports and module usage.
The imports are well-organized and relevant to the component's functionality:
dioxus::prelude::*for Dioxus core functionalities.crate::components::task_list::TaskListseems unused in this file and could be removed unless it's intended for future use.crate::models::category::Categoryandcrate::route::Routeare essential for handling routing and category data.Consider removing unused imports to keep the code clean and efficient.
Review of imports and module usage.
The imports are well-organized and relevant to the component's functionality:
dioxus::prelude::*for Dioxus core functionalities.crate::components::task_list::TaskListseems unused in this file and could be removed unless it's intended for future use.crate::models::category::Categoryandcrate::route::Routeare essential for handling routing and category data.Consider removing unused imports to keep the code clean and efficient.