kraus-s
commented
2 years ago This is proving more difficult to accomplish. Nested buttons, i.e. buttons that are nested in multiple instances of with st.something, will by default trigger a rerun. This cannot be prevented and is the very session states were implemented in the first place. Sort of forgot about that myself. So we will still need the state handler. However, we can greatly reduce complexity by using st.empty(). Not sure about getting rid of all of the st.experimental_rerun() instances BUT: What we can do is get rid of the meta functions, that select the search or result function and instead combine those in the search function, which will check, if there are results and then empty the container and fill it with the results container. Alternatively, the container could live at the level of the meta function and be filled with either content.
BalduinLandolt
The current implementation of steps is rather clumsy.
Essentially, where ever
st.experimental_rerun()is called, that is, because we want to get rid of the previous step. But that way, we need to keep track of steps by using the steps in the state handler, and need to persist search results and stuff there too.With a Streamlit's empty container, we could solve this in a much simpler way, as it allows to get rid of previous stuff by simply clearing the container. Then no re-run is required any more, thus no steps and intermediate data is needed either. So we should be able to get rid of this, if not the entire
StateHandleras a whole.