fix(PageComponent): update saveFlow function to pass a modified flow object with updated data property to improve data consistency
fix(extraSidebarComponent): update saveFlow function to pass a modified flow object with updated data property to improve data consistency
fix(API): update parameter name from status to isPrivate for consistency and clarity
fix(StorePage): update parameter name from status to isPrivate to match API changes and improve semantics
🔧 chore(service.py): remove duplicate import of logger from loguru module
🔧 chore(service.py): add "private" field to the list of fields to retrieve from the store API
🐛 fix(test_database.py): fix function call to Flow.model_validate
🐛 fix(test_llms_template.py): fix values in test cases
🔥 chore(test_store.py): remove unused test file and test case
🔧 fix(utils.py): replace requests library with httpx library for getting latest released version of langflow from PyPI to improve performance and reliability
The saveFlowStore function in the API controller now includes a new parameter called "private". This parameter is used to determine whether the flow should be saved as a private flow or not. If the "publicFlow" variable is false, the "private" parameter will be set to true, indicating that the flow should be saved as a private flow. The "status" field in the saved flow object is also updated accordingly to reflect the flow's privacy status.
✨ feat(store.py): add support for private query parameter in get_components function to filter components by privacy
🐛 fix(schema.py): set default value of private field in StoreComponentCreate schema to True
🐛 fix(service.py): change status field to private field in build_filter_conditions and get_list_component_response_model functions to filter components by privacy
fix(API/index.ts): fix BASE_URL_API missing slash causing incorrect API endpoint URL
fix(StorePage/index.tsx): add catch block to handle error when fetching store tags and log error message
🔀 merge(exceptions.py): add custom exceptions with status codes to handle specific errors in the store service
🔀 merge(service.py): replace ValueError with custom exceptions in the store service to provide more specific error messages and status codes
The text in the StorePage component was updated to be more generic and inclusive. Instead of saying "You haven't created/liked any flows yet", it now says "You haven't created/liked anything yet". This change was made to make the text more inclusive and applicable to different types of content, not just flows.
