Skip to content

Update example in button guide #1214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sfc-gh-dmatthews merged 1 commit into from
Dec 24, 2024
Merged

Update example in button guide #1214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions content/develop/concepts/app-design/button-behavior-and-examples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -365,10 +365,8 @@ if 'processed' not in st.session_state:
if st.button('Process'):
result = expensive_process(option, add)
st.session_state.processed[option] = result

if option in st.session_state.processed:
st.write(f'Option {option} processed with add {add}')
st.write(st.session_state.processed[option][0])
result[0]
```

Astute observers may think, "This feels a little like caching." We are only saving results relative to one parameter, but the pattern could easily be expanded to save results relative to both parameters. In that sense, yes, it has some similarities to caching, but also some important differences. When you save results in `st.session_state`, the results are only available to the current user in their current session. If you use [`st.cache_data`](/develop/api-reference/caching-and-state/st.cache_data) instead, the results are available to all users across all sessions. Furthermore, if you want to update a saved result, you have to clear all saved results for that function to do so.
Expand Down