refactor(MainPage): comment out code that adds "From Store" sidebar navigation item
feat(flow): add date_created property to FlowType to track the creation date of flows
🚀 feat(store.py): add support for pagination in get_components endpoint to limit the number of results returned
🔧 fix(store.py): fix count_components endpoint to handle cases where the number of results is less than the limit
fix(market-card.tsx): set loading state to false after postLikeComponent promise is resolved or rejected to stop the loading state
fix(market-card.tsx): disable the like button when loading state is true or authorized state is false to prevent multiple requests and provide visual feedback to the user
feat(StoreApiKeyModal/index.tsx): add support for checking if an API key exists in the StoreContext
fix(market-card.tsx): remove unnecessary code for handling installable market cards
The sorting order in the API request for popular pages was using the "liked_by" field instead of the correct "downloads" field. This commit fixes the sorting order to use the correct field, ensuring that popular pages are sorted based on the number of downloads.
✨ feat(store.py): add support for user_data_context to fetch and set user data to the context variable
🐛 fix(store.py): handle HTTPStatusError when fetching user data and raise ValueError for invalid API key
🐛 fix(service.py): handle HTTPStatusError when fetching user data and raise ValueError for invalid API key
🐛 fix(service.py): return count as int in count_components method
The logic for setting the totalRowsCount in the StorePage component has been updated. Previously, it was only considering the count returned from the API response. Now, it takes into account the length of the filteredCategories array as well. If the filteredCategories array is empty, the totalRowsCount is set to the count returned from the API response. Otherwise, it is set to the length of the results array in the API response. This change ensures that the totalRowsCount accurately reflects the number of rows in the search results, taking into account any applied filters.
Also, the condition for rendering the PaginatorComponent has been updated. Previously, it was checking if the loading state is false or the searchData array is not empty. Now, it only checks if the loading state is false and the searchData array is not empty. This change ensures that the PaginatorComponent is only rendered when the loading state is false and there are search results available.
refactor(tabsContext.tsx): update processFlows function to handle removing flows from state
fix(extraSidebarComponent/index.tsx): remove unused code that caused bugs
fix(extraSidebarComponent/sideBarDraggableComponent/index.tsx): update deleteComponent function to remove count from item name
fix(StorePage): fix className prop on Button component to correctly apply error styling
fix(StorePage): fix className prop on IconComponent to correctly apply loading animation
fix(StorePage): fix onClick event on IconComponent to correctly update searchText state
fix(StoreApiKeyModal): remove the "Sign up" button and replace it with a text link to langflow.store
fix(StoreApiKeyModal): change the position and styling of the text link to langflow.store
fix(StoreApiKeyModal): change the "Cancel" button to be aligned with the "Save" button
fix(StoreApiKeyModal): wrap the "Save" button in a Form.Submit component for better form handling
The variable `result` is updated with the value of `updated_result` after calling the `update_components_with_user_data` function. This change improves code readability and makes the intention clearer.
