feat: ability to create a project #9
@ -1,5 +1,4 @@
|
||||
|
|
||||
use crate::components::project_form::ProjectForm;
|
||||
use crate::server::projects::{create_project, testing};
|
||||
Consider adding error handling for the The **Consider adding error handling for the `create_project` call.**
The `create_project` function is called asynchronously, but any potential errors are currently ignored. Consider handling errors to improve robustness and provide feedback to users.
```rust
onsubmit: move |title| {
spawn(async move {
if let Err(e) = create_project(title).await {
// Handle the error, e.g., log it or display a message to the user
}
});
}
```
<!-- This is an auto-generated reply by CodeRabbit -->
This will be addressed in a later development stage. The project creation should probably result in a redirect. This will be addressed in a later development stage. The project creation should probably result in a redirect.
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out. <!-- [monologue]
[observations] The user plans to handle error management and possibly implement a redirect after project creation in a future development stage.
[analysis] Since the user has acknowledged the suggestion and plans to address it later, there's no immediate action required. It's important to acknowledge their plan and offer assistance if needed.
[actions] Respond to the user acknowledging their plan and offering further assistance if required.
-->
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out.
<!-- This is an auto-generated reply by CodeRabbit -->
|
||||
use dioxus::core_macro::rsx;
|
||||
use dioxus::dioxus_core::Element;
|
||||
use dioxus::prelude::*;
|
||||
|
||||
|
Consider adding error handling for the The **Consider adding error handling for the `create_project` call.**
The `create_project` function is called asynchronously, but any potential errors are currently ignored. Consider handling errors to improve robustness and provide feedback to users.
```rust
onsubmit: move |title| {
spawn(async move {
if let Err(e) = create_project(title).await {
// Handle the error, e.g., log it or display a message to the user
}
});
}
```
<!-- This is an auto-generated reply by CodeRabbit -->
Consider adding error handling for the The **Consider adding error handling for the `create_project` call.**
The `create_project` function is called asynchronously, but any potential errors are currently ignored. Consider handling errors to improve robustness and provide feedback to users.
```rust
onsubmit: move |title| {
spawn(async move {
if let Err(e) = create_project(title).await {
// Handle the error, e.g., log it or display a message to the user
}
});
}
```
<!-- This is an auto-generated reply by CodeRabbit -->
This will be addressed in a later development stage. The project creation should probably result in a redirect. This will be addressed in a later development stage. The project creation should probably result in a redirect.
This will be addressed in a later development stage. The project creation should probably result in a redirect. This will be addressed in a later development stage. The project creation should probably result in a redirect.
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out. <!-- [monologue]
[observations] The user plans to handle error management and possibly implement a redirect after project creation in a future development stage.
[analysis] Since the user has acknowledged the suggestion and plans to address it later, there's no immediate action required. It's important to acknowledge their plan and offer assistance if needed.
[actions] Respond to the user acknowledging their plan and offering further assistance if required.
-->
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out.
<!-- This is an auto-generated reply by CodeRabbit -->
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out. <!-- [monologue]
[observations] The user plans to handle error management and possibly implement a redirect after project creation in a future development stage.
[analysis] Since the user has acknowledged the suggestion and plans to address it later, there's no immediate action required. It's important to acknowledge their plan and offer assistance if needed.
[actions] Respond to the user acknowledging their plan and offering further assistance if required.
-->
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out.
<!-- This is an auto-generated reply by CodeRabbit -->
|
||||
Consider adding error handling for the
create_projectcall.The
create_projectfunction is called asynchronously, but any potential errors are currently ignored. Consider handling errors to improve robustness and provide feedback to users.Consider adding error handling for the
create_projectcall.The
create_projectfunction is called asynchronously, but any potential errors are currently ignored. Consider handling errors to improve robustness and provide feedback to users.This will be addressed in a later development stage. The project creation should probably result in a redirect.
This will be addressed in a later development stage. The project creation should probably result in a redirect.
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out.
@matous-volf, that sounds like a good plan. If you need any assistance with implementing error handling or the redirect in the future, feel free to reach out.