feat: basic TODO app; no bells, no whistles

[jdevries3133]

I was wishing this was present when trying to learn from the examples in the repo – just a basic client-side TODO app without any server-side code or isomorphism.

I feel like this specific implementation probably stinks – I'm totally new to both Leptos and Rust, so happy to take any feedback & no hard feelings if there isn't interest in pulling an example like this into the repo. I fully appreciate my naive perspective here :)

[phillipbaird]

Would Vec.retain() be a simpler way to implement delete_todo?

[jdevries3133]

Would Vec.retain() be a simpler way to implement delete_todo?

Yeah, that's a definite improvement, thank you!

[gbj]

Thanks for suggesting this! When compared to the todomvc (which is a standard cross-framework example, and is also just client-side-only with no server-side code), is the idea here just that this is even simpler? I think otherwise the basics of a simple component, then iteration are pretty well demonstrated by counter and counters.

[jdevries3133]

Maybe this could be called todo_component? I think that not everyone is familiar with the MVC pattern, and this is line-for-line akin to a todo list app that you might see taught to React developers. Nonetheless, my feelings won't be hurt if you think this doesn't fit! I think you are right that the same ideas are represented already in other examples.

[flosse]

I'd split the ID, the Todo and the latest ID state.

e.g.:

#[derive(Debug, Default, Clone, Copy, PartialEq, Eq, Hash)]
pub struct TodoId(u64);

impl TodoId {
    const fn next(self) -> Self {
        Self(self.0 + 1)
    }
}

impl TodoItem {
    const fn new(id: TodoId, name: String) -> Self {
        Self { id, name }
    }
}

fn main(){
    let mut current_id = TodoId::default();
    // ...
    let create_new_item = |title| {
        let next_id = current_id.next();
        current_id = next_id;       
        let todo = TodoItem::new(next_id, title);
    };
}

[gbj]

@jdevries Sorry for my slow response here. Thanks for your contribution. We have created a new projects directory to house a wider variety of projects without the same maintenance burden as examples — Would you be interested in updating your PR and adding it to projects instead? I totally understand if not, it's been a while :-)

[gbj]

@jdevries Sorry for my slow response here. Thanks for your contribution. We have created a new projects directory to house a wider variety of projects without the same maintenance burden as examples — Would you be interested in updating your PR and adding it to projects instead? I totally understand if not, it's been a while :-)