Sending messages during the rendering phase can cause infinite update loops

[jstarry]

Suggested changes

Option 1. Update the scheduler queue to prevent this
Option 2. Update documentation to warn against this behaviour

[mc1098]

#2040 documents this behaviour so I think the documentation label can be removed now.

[siku2]

Closing this because it's documented behaviour now. If there's a need for the scheduler to be changed, a new issue should be opened.

[zelds]

    let (store, dispatch) = use_store::<Store>();
    let history = use_navigator().unwrap();
    let projects = use_state(Vec::new);


    if store.token.is_empty() {
        dispatch.reduce_mut(move |store| {
            store.error_message = "Please create account or login.".to_owned()
        });
        history.push(&Route::Login)
    }
    {
        let projects = projects.clone();
        use_effect(move || {
            spawn_local(async move {
                match get_projects(&store.token).await {
                    Ok(user_projects) => projects.set(user_projects),
                    Err(APIError::NotAuthenticated) => dispatch.reduce_mut(move |store| {
                        store.token = String::new();
                        store.email = String::new();
                    }),
                    Err(error) => {
                        log!(error.to_string())
                    }
                }
            });
        });
    };

I try to prevent loop using loaded = use_state(false) but in this case works ok for first load. And if I delete "project" from different component, using REST and use navigator to redirect to this component, its freezes, and show same data as it is at first render (without requesting REST again). Try to understand how to fix it, or atleast bypass.