feat(flowsContext.tsx): add support for version property in FlowsProvider to store and retrieve the version of the app
fix(exportModal/index.tsx): change version property to last_tested_version to match FlowType definition
fix(extraSidebarComponent/index.tsx): add version property to saveFlowStore function call to match FlowType definition
fix(extraSidebarComponent/sideBarDraggableComponent/index.tsx): add version property to downloadNode function call to match FlowType definition
fix(nodeToolbarComponent/index.tsx): add version property to saveFlowStore function call to match FlowType definition
fix(FlowPage/index.tsx): add version property to useContext to prevent undefined errors
fix(ViewPage/index.tsx): add version property to useContext to prevent undefined errors
fix(flow/index.ts): change version property to last_tested_version to match FlowType definition
fix(tabs/index.ts): add version property to FlowsContextType to prevent undefined errors
fix(reactflowUtils.ts): change createFlowComponent function signature to include version parameter
The version field is added to the exported flow data in order to keep track of the version of the flow. This allows for better management and identification of different versions of the flow.
fix(exportModal): fetch and set version from API
The version is fetched from the API using the `getVersion` function and then set in the state variable `version` using the `setVersion` function. This ensures that the correct version is used when exporting the flow.
feat(flow): add version field to FlowType
The `FlowType` interface is updated to include a `version` field. This allows for storing and retrieving the version of the flow when needed.
✨ feat(store.py): add support for checking if store has a valid API key using the StoreService
🐛 fix(service.py): remove unused import and fix formatting
✨ feat(service.py): add check_api_key method to StoreService to check if an API key is valid
🐛 fix(service.py): import logger from loguru module to fix logger import error
✨ feat(service.py): add support for metadata in _get method to handle additional metadata returned in API response
✨ feat(service.py): add support for metadata in query_components method to handle additional metadata returned in API response
fix(API/index.ts): remove unused import and modify getStoreComponents function to accept an object with optional parameters for better readability and maintainability
fix(from-store/index.tsx): modify handleGetComponents function to pass an object with optional parameters to getStoreComponents for better readability and maintainability
fix(StorePage/index.tsx): modify handleGetComponents function to pass an object with optional parameters to getStoreComponents for better readability and maintainability
🐛 fix(store.py): fix the call to get_component_likes_count method by removing api_key parameter since it's not needed
🐛 fix(service.py): fix the return type of _get method to always return a list of dictionaries
🐛 fix(service.py): fix the call to get_component_likes_count method by removing api_key parameter since it's not needed
🐛 fix(service.py): remove unnecessary import statement for logger
✨ feat(store.py): add support for filtering components by liked status and store API key
✨ feat(service.py): add build_liked_filter method to build filter conditions based on liked status and store API key
🔧 chore(service.py): change user_data_context from contextmanager to asynccontextmanager to support asynchronous operations
🔧 chore(service.py): handle case when user_data is a list and take the first element
🔧 chore(service.py): remove liked and api_key parameters from get_components method and handle public components separately
🔧 chore(service.py): handle case when results is a dictionary and convert it to a list of results_objects
🐛 fix(service.py): add filter_by_user parameter to StoreService's get_components method to enable filtering components by user
🐛 fix(index.ts): add filterByUser parameter to getStoreComponents function to enable filtering components by user
