Metadata-Version: 2.1
Name: octostar-streamlit-search-experience
Version: 0.1.0
Summary: 
License: MIT
Author: Your Name
Author-email: you@example.com
Requires-Python: >=3.9, !=2.7.*, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*, !=3.6.*, !=3.7.*, !=3.8.*
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Dist: streamlit (>=1.34.0,<2.0.0)
Requires-Dist: streamlit-octostar-research (>=0.1.22,<0.2.0)
Description-Content-Type: text/markdown

# Octostar search experience streamlit component

Motivation to create a separate project for the component is to address problems with complex bidirectional components in Streamlit. The problem with the current search experience implementation is that Streamlit resets the state of the application each time a component returns a value what makes usage of conditions with UI components difficult.

Therefore, instead of spliting work with search experience into "trigger" and "get value" parts the easier way is to encapsulate work with the Octostar platform API inside a separate component what enables such component to set the value for Streamlit in whatever convenient way.

## Related resources

- https://streamlit-components-tutorial.netlify.app/introduction/;

