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.
fix(pages): add support for disabling StoreApiKeyModal button when loading prop is true
feat(types): add disabled prop to StoreApiKeyType to enable/disable StoreApiKeyModal component
Add a message to the StorePage component to inform the user that they haven't crafted or liked any flows yet. This message encourages the user to create a flow by giving it a shot. The message is displayed when the loading is complete and the searchData array is empty.
The setValidApiKey function call was unnecessary and not being used in the StorePage component. Removing it improves code readability and removes unnecessary code execution.
The code was checking for the presence of an API Key and displaying an error message if it was missing or invalid. However, this logic is no longer needed as the API Key is now always required and validated before reaching this point. Therefore, the code that handles the case of an invalid API Key is no longer necessary and has been removed for simplicity and clarity.
