The `saveFlowStore` function in the API controller now accepts an optional `last_tested_version` parameter. This parameter allows the user to specify the last tested version of a flow when saving it to the flow store. The value of `last_tested_version` is now included in the request payload when creating a new flow in the flow store.
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.
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(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
fix(extraSidebarComponent): fix useEffect dependency warning by adding getFilterEdge to the dependency array
fix(utils): refactor groupByFamily function to use nodeGroupedObjType type for tempInputs and tempOutputs arrays
feat(extraSidebarComponent/index.tsx): add support for filtering data based on selected filter edges
fix(components/index.tsx): fix import statement for FlowsContext in order to use the correct context
refactor(market-card): update import statement in MarketCardComponent to use FlowsContext instead of TabsContext
refactor(store-page): remove unused setTabId function from StorePage component
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
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
