Reduces number of total RPC calls on Pools page #1518
Conversation
abtestingalpha
requested review from
bigboydiamonds,
nautsimon and
aureliusbtc
as code owners
WalkthroughThe changes primarily focus on enhancing the performance and reliability of the Synapse Interface. This is achieved by memoizing components, adding type annotations, and introducing a new state variable Changes
TipsChat with CodeRabbit Bot (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (10)
- packages/synapse-interface/components/Pools/PoolCardBody.tsx (2 hunks)
- packages/synapse-interface/components/Pools/PoolHeader.tsx (1 hunks)
- packages/synapse-interface/contexts/UserProvider.tsx (5 hunks)
- packages/synapse-interface/pages/pool/PoolBody.tsx (3 hunks)
- packages/synapse-interface/pages/pool/[poolId].tsx (2 hunks)
- packages/synapse-interface/pages/pools/PoolCard.tsx (3 hunks)
- packages/synapse-interface/pages/pools/PoolCards.tsx (1 hunks)
- packages/synapse-interface/utils/actions/getPoolApyData.ts (2 hunks)
- packages/synapse-interface/utils/actions/getPoolData.ts (4 hunks)
- packages/synapse-interface/utils/types/index.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
- packages/synapse-interface/contexts/UserProvider.tsx
Additional comments: 27
packages/synapse-interface/utils/types/index.tsx (1)
- 49-51: The
virtualPriceandswapFeeproperties of thePoolDatatype have been made optional. Ensure that all uses of these properties throughout the codebase are updated to handle the possibility of these properties beingundefined.packages/synapse-interface/pages/pools/PoolCards.tsx (3)
5-12: The addition of
useAppSelectorto fetchsynPrices,ethPrice, andavaxPricefrom the state is a good practice. It helps to avoid prop drilling and makes the component more maintainable. However, ensure that the state is updated correctly before this component is rendered to avoid potential issues.14-16: The early return when
ethPriceis not available is a good practice. It prevents the component from rendering when the necessary data is not available.31-37: The
PoolCardcomponent now receives additional propsethPrice,avaxPrice, andsynPrices. Ensure that thePoolCardcomponent has been updated to handle these new props correctly.packages/synapse-interface/pages/pool/[poolId].tsx (2)
40-49: The introduction of the
isClientstate variable and setting it totrueon component mount is a good way to ensure that certain effects and data fetches only execute on the client side. This can help optimize the number of RPC calls.70-74: The addition of
isClientto the dependency array of theuseEffecthook and the conditional check forisClientbefore dispatchingresetPoolDataandfetchPoolDataactions ensures that these actions are only dispatched on the client side. This is a good optimization to reduce the number of RPC calls.packages/synapse-interface/components/Pools/PoolHeader.tsx (3)
12-13: The
PoolHeadercomponent is now wrapped with thememofunction from React. This is a performance optimization that helps to avoid unnecessary re-renders of the component by memoizing the output of the component and only re-rendering if the props have changed.14-36: The logic inside the
PoolHeadercomponent remains the same. It uses theuseNetworkhook to get the connected chain, theusePortfolioStatehook to get portfolio-related state information, and theuseMemohook to calculate thecanDepositvariable.37-64: The render logic of the
PoolHeadercomponent remains the same. It renders a header section with pool information and a deposit link if certain conditions are met.packages/synapse-interface/pages/pool/PoolBody.tsx (3)
30-32: The introduction of the
isClientstate variable is a good approach to prevent unnecessary RPC calls on the server side. This variable is set totruewhen the component mounts, indicating that the component is on the client side.44-46: The
useEffecthook is used to setisClienttotruewhen the component mounts. This is a good practice to ensure that the component knows when it's being rendered on the client side.36-57: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [48-69]
The
useEffecthook now checks forisClientbefore executing its logic. This is a good practice to prevent unnecessary RPC calls on the server side. However, it's important to note that this change might affect the timing of thesegmentAnalyticsEventandgetStakedBalancecalls. Make sure that these calls still work as expected and that they don't rely on being executed immediately when the component mounts.packages/synapse-interface/components/Pools/PoolCardBody.tsx (3)
1-4: The new hunk imports the
memofunction from React and theTokentype from the local utility types. This is a good practice as it helps to avoid unnecessary re-renders of the components, improving the performance of the application.7-40: The
PoolCardBodycomponent is now wrapped with thememofunction from React. This is a good practice as it helps to avoid unnecessary re-renders of the component, improving the performance of the application. The props are also now explicitly typed, which improves code readability and maintainability.1-45: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [42-84]
The
PoolTokenIconscomponent is now wrapped with thememofunction from React. This is a good practice as it helps to avoid unnecessary re-renders of the component, improving the performance of the application. The props are also now explicitly typed, which improves code readability and maintainability.packages/synapse-interface/utils/actions/getPoolApyData.ts (2)
- 2-8: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [1-8]
The import of
fetchBalanceandfetchTokenhas been removed and replaced witherc20ABI. This change is in line with the PR's goal of reducing RPC calls by using multicall to fetch data in a single call.
- 51-71: The
fetchBalanceandfetchTokencalls have been replaced with multicall calls using theerc20ABIABI to fetchbalanceOfandtotalSupply. This change reduces the number of RPC calls, improving performance.- const lpTokenBalanceResult = - ( - await fetchBalance({ - address: minichefAddress, - chainId, - token: poolToken.addresses[chainId] as Address, - }) - )?.value ?? 0n - - const lpTokenSupplyResult = - ( - await fetchToken({ - address: poolToken.addresses[chainId] as Address, - chainId, - }) - )?.totalSupply?.value ?? 0n + const lpTokenBalanceResult: bigint = data[3].result ?? 0n + const lpTokenSupplyResult: bigint = data[4].result ?? 0npackages/synapse-interface/pages/pools/PoolCard.tsx (7)
8-13: The import of
useAppSelectorhas been removed and no new imports have been added. Ensure thatuseAppSelectoris not used anywhere else in the code. If it is, replace it with an appropriate alternative.21-31: The function signature of
PoolCardhas been changed. It now takesethPrice,avaxPrice, andsynPricesas props. Ensure that all calls toPoolCardthroughout the codebase have been updated to match the new signature.32-44: A new state variable
isClienthas been introduced and is set totruewhen the component mounts. This variable is used to conditionally execute effects and fetch data only when the component is on the client side. This is a good practice to prevent unnecessary data fetching on the server side.46-68: The
useEffecthook has been updated to fetch pool data and pool APY data only whenisClientistrue. This is a good practice to prevent unnecessary data fetching on the server side.70-86: The
useEffecthook has been updated to fetch staked balance only whenisClientistrue. This is a good practice to prevent unnecessary data fetching on the server side.101-110: No significant changes have been made in this hunk. The code formatting has been altered slightly, but the functionality remains the same.
113-114: The
PoolHeadercomponent now receivesaddressas a prop. Ensure that thePoolHeadercomponent has been updated to handle this new prop.packages/synapse-interface/utils/actions/getPoolData.ts (3)
1-8: The imports have been updated to include
erc20ABIandmulticallfrom@wagmi/core, andlpTokenABIandSWAP_ABIfrom@/constants/abis. This is in line with the PR's goal of reducing RPC calls by usingmulticalland fetchingbalanceOfandtotalSupplyusing theerc20ABIABI.118-123: The
getSinglePoolDatafunction no longer fetchesswapFeeandvirtualPricefromgetCorePoolData. This is in line with the PR's summary, which states thatgetSinglePoolDatano longer includesvirtualPriceandswapFeein its return value. Ensure that this change does not break any functionality that relies on these values.144-148: The returned
PoolDataobject no longer includesvirtualPriceandswapFee. This is in line with the PR's summary, which states that thePoolDatainterface has been updated to reflect these changes. Ensure that this change does not break any functionality that relies on these values.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1518 +/- ##
=============================================
Coverage 50.81006% 50.81006%
=============================================
Files 357 357
Lines 23887 23887
Branches 279 279
=============================================
Hits 12137 12137
Misses 10596 10596
Partials 1154 1154
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
abtestingalpha
force-pushed
the
fe/reduce-rpc-calls
branch
from
fbac8f9 to
8411a60
Compare
Deploying with
|
| Latest commit: |
84d568e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b7f10b8f.sanguine.pages.dev |
| Branch Preview URL: | https://fe-reduce-rpc-calls.sanguine.pages.dev |
There was a problem hiding this comment.
Review Status
Actionable comments generated: 3
Configuration used: CodeRabbit UI
Commits
Files that changed from the base of the PR and between f75a32b and 8411a60166b09b041cd84ce3e8854ce7ee228d66.Files selected for processing (10)
- packages/synapse-interface/components/Pools/PoolCardBody.tsx (2 hunks)
- packages/synapse-interface/components/Pools/PoolHeader.tsx (1 hunks)
- packages/synapse-interface/contexts/UserProvider.tsx (5 hunks)
- packages/synapse-interface/pages/pool/PoolBody.tsx (3 hunks)
- packages/synapse-interface/pages/pool/[poolId].tsx (2 hunks)
- packages/synapse-interface/pages/pools/PoolCard.tsx (3 hunks)
- packages/synapse-interface/pages/pools/PoolCards.tsx (1 hunks)
- packages/synapse-interface/utils/actions/getPoolApyData.ts (2 hunks)
- packages/synapse-interface/utils/actions/getPoolData.ts (4 hunks)
- packages/synapse-interface/utils/types/index.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
- packages/synapse-interface/utils/actions/getPoolApyData.ts
Additional comments: 28
packages/synapse-interface/utils/types/index.tsx (1)
- 46-52: The
virtualPriceandswapFeeproperties in thePoolDatatype are now optional. This change should be reflected in all parts of the codebase wherePoolDatais used. Ensure that all instances ofPoolDataare checked for the existence ofvirtualPriceandswapFeebefore they are used.packages/synapse-interface/pages/pool/[poolId].tsx (2)
37-49: The introduction of the
isClientstate variable and setting it totrueon component mount is a good practice to prevent unnecessary data fetching on the server side. This can improve performance and reduce the number of RPC calls.70-74: The conditional check for
poolIdandisClientbefore dispatching actions and fetching pool data is a good practice. It ensures that data is only fetched when necessary and on the client side, which can improve performance and reduce the number of RPC calls.packages/synapse-interface/components/Pools/PoolHeader.tsx (1)
- 1-68: The use of
memoto wrap thePoolHeadercomponent is a good practice as it prevents unnecessary re-renders of the component, improving the performance of the application. The use ofuseMemoforcanDepositis also a good practice as it ensures that the function is only re-computed whenpool,balancesAndAllowances, oraddresschanges. This also helps in improving the performance of the application. The type annotations forpoolandaddressprovide better type safety. The use oflodashfor operations likepickBy,get, andsomeprovides a more readable and maintainable code.packages/synapse-interface/components/Pools/PoolCardBody.tsx (3)
1-4: Imports look good and are correctly ordered.
7-40: The
PoolCardBodycomponent is correctly memoized and the props are properly typed. This will help to avoid unnecessary re-renders and improve performance.1-45: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [42-84]
The
PoolTokenIconscomponent is correctly memoized and the props are properly typed. This will help to avoid unnecessary re-renders and improve performance.packages/synapse-interface/pages/pool/PoolBody.tsx (2)
30-33: The introduction of the
isClientstate variable is a good practice to prevent unnecessary data fetching and effects execution on the server side. This can improve performance and reduce the number of RPC calls.45-46: This effect sets
isClienttotruewhen the component mounts, which is a common pattern to determine if the code is running on the client side.packages/synapse-interface/contexts/UserProvider.tsx (6)
1-4: The import statements look fine. No issues found.
18-24: The introduction of the
isClientstate variable is a good way to ensure that certain effects only run on the client side. This can help to improve performance by reducing unnecessary server-side computations.44-46: This effect sets
isClienttotruewhen the component mounts. This is a common pattern for distinguishing between server-side and client-side rendering in React.48-54: This effect fetches price data when
isClientistrue. This is a good way to ensure that these fetch actions only run on the client side, which can help to improve performance.56-58: This effect sets the swap chain ID when
chainchanges. This is a good way to keep the swap chain ID in sync with the current chain.78-84: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [78-93]
This effect fetches and stores portfolio balances when
isClient,address, andchain.idare truthy. This is a good way to ensure that this fetch action only runs on the client side and when the necessary data is available. The error handling in this effect is also good, as it logs an error message if the fetch action fails.packages/synapse-interface/pages/pools/PoolCards.tsx (3)
2-41: The
PoolCardscomponent is memoized usingReact.memo. This is a good practice for performance optimization as it prevents unnecessary re-renders of the component when the props do not change. However, it's important to note thatReact.memoonly does a shallow comparison of props. If the props are complex objects, changes inside these objects may not trigger a re-render. In this case,poolsis an object andsynPricesis also likely to be an object. If these objects are being mutated directly somewhere in the code, the component may not re-render as expected. Consider using deep comparison or immutable data structures to ensure the component re-renders correctly when the data changes.14-16: The component returns
nullifethPriceis falsy. This is a good practice for conditional rendering based on data availability. However, it's important to ensure that the parent component can handle the case wherePoolCardsreturnsnull, to avoid any potential layout issues.31-38: The
PoolCardcomponent is being rendered with additional props (ethPrice,avaxPrice,synPrices). Ensure that thePoolCardcomponent has been updated to accept and correctly use these new props.packages/synapse-interface/pages/pools/PoolCard.tsx (5)
18-31: The
PoolCardcomponent has been updated to use thememofunction from React. This is a good practice as it helps to avoid unnecessary re-renders of the component, improving the performance of the application. However, ensure that the props passed toPoolCardare not deeply nested objects or arrays, asmemoonly does a shallow comparison of props. If the props are deeply nested objects or arrays, consider using a library like lodash'sisEqualfor deep comparison or normalize the data structure.32-38: The
isClientstate variable is initialized tofalseand then set totruein auseEffecthook. This is a common pattern used to prevent server-side rendering (SSR) of client-side code. It's a good practice for improving performance and avoiding errors related to accessing browser-specific APIs during SSR.46-68: The
getSinglePoolDataandgetPoolApyDatafunctions are now called withpool.chainIdinstead ofchainId. This change should be fine as long aspool.chainIdis always defined and valid when these functions are called. Also, these functions are now only called ifisClientistrue, which is a good practice to prevent unnecessary data fetching on the server side.70-86: The
getStakedBalancefunction is now called withpool.chainIdandpool.poolId[pool.chainId]instead ofchainIdandpool.poolId[chainId]. This change should be fine as long aspool.chainIdandpool.poolId[pool.chainId]are always defined and valid when this function is called. Also, this function is now only called ifaddressis truthy andisClientistrue, which is a good practice to prevent unnecessary data fetching on the server side.113-117: The
PoolHeadercomponent is now called withaddress as Addressinstead ofaddress. This change should be fine as long asaddressis always a validAddresswhen this component is rendered.packages/synapse-interface/utils/actions/getPoolData.ts (5)
1-9: The import statements have been reorganized and new imports have been added. Ensure that these new imports are used correctly in the code and that they are necessary for the functionality of the code.
18-94: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [10-20]
The function signature for
getBalanceDataremains the same. No changes needed here.
70-93: The function now calculates the
lpTotalSupplyandtokenBalancesusing the results from themulticall. This is a good optimization that reduces the number of RPC calls. However, ensure that themulticallDataarray always has the expected length and structure to avoid potential runtime errors.118-123: The
getSinglePoolDatafunction now fetches theethPriceandavaxPriceif they are not provided in thepricesargument. This is a good fallback mechanism that ensures the function always has the necessary data to perform its calculations.144-147: The
getSinglePoolDatafunction no longer includesvirtualPriceandswapFeein its return value. Ensure that this change does not break any code that relies on these properties.
abtestingalpha
force-pushed
the
fe/reduce-rpc-calls
branch
from
8411a60 to
8ec904b
Compare
- memoizes components - uses isClient/setClient for useEffects with rpc calls to prevent double calls
abtestingalpha
force-pushed
the
fe/reduce-rpc-calls
branch
from
8ec904b to
84d568e
Compare
There was a problem hiding this comment.
Review Status
Actionable comments generated: 6
Configuration used: CodeRabbit UI
Files selected for processing (10)
- packages/synapse-interface/components/Pools/PoolCardBody.tsx (2 hunks)
- packages/synapse-interface/components/Pools/PoolHeader.tsx (1 hunks)
- packages/synapse-interface/contexts/UserProvider.tsx (5 hunks)
- packages/synapse-interface/pages/pool/PoolBody.tsx (3 hunks)
- packages/synapse-interface/pages/pool/[poolId].tsx (2 hunks)
- packages/synapse-interface/pages/pools/PoolCard.tsx (3 hunks)
- packages/synapse-interface/pages/pools/PoolCards.tsx (1 hunks)
- packages/synapse-interface/utils/actions/getPoolApyData.ts (2 hunks)
- packages/synapse-interface/utils/actions/getPoolData.ts (4 hunks)
- packages/synapse-interface/utils/types/index.tsx (1 hunks)
Additional comments: 32
packages/synapse-interface/utils/types/index.tsx (1)
- 46-52: The
virtualPriceandswapFeeproperties in thePoolDatatype are now optional. This change should be reflected in all parts of the codebase wherePoolDatais used. Ensure that the code can handle cases where these properties are undefined.totalLocked: number totalLockedUSD: number - virtualPrice: bigint + virtualPrice?: bigint nativeTokens?: any - swapFee: bigint + swapFee?: bigintpackages/synapse-interface/pages/pools/PoolCards.tsx (2)
2-41: The
PoolCardscomponent is memoized which is a good practice for performance optimization. It prevents unnecessary re-renders of the component when the props haven't changed. However, ensure that the props passed to this component are also memoized or are primitive values to fully benefit from this optimization.31-38: The
PoolCardcomponent is being passed additional props (ethPrice,avaxPrice,synPrices). Ensure that these props are being used appropriately within thePoolCardcomponent and that they don't introduce unnecessary re-renders.packages/synapse-interface/pages/pool/[poolId].tsx (3)
37-40: The introduction of the
isClientstate variable is a good practice to prevent unnecessary data fetching and effects on the server side. This can improve performance and reduce server load.47-49: This
useEffecthook setsisClienttotruewhen the component mounts, which is a common pattern to determine if the code is running on the client side.69-74: This
useEffecthook now only dispatches theresetPoolDataaction and fetches pool data ifpoolIdis truthy andisClientistrue. This is a good practice to prevent unnecessary data fetching and effects on the server side.packages/synapse-interface/pages/pool/PoolBody.tsx (3)
27-33: The introduction of the
isClientstate variable and its initialization tofalseis a good practice to prevent unnecessary data fetching and effects on the server side. This can improve performance and reduce the number of RPC calls.36-57: The changes made to the effects that fetch data and set the
stakedBalancestate variable are correct. The effects now only run on the client side, which can improve performance and reduce the number of RPC calls. TheisClientvariable is correctly included in the dependency array of these effects to ensure they run when its value changes.66-69: The
isClientvariable is correctly included in the dependency array of the effect that sets thestakedBalancestate variable. This ensures that the effect runs when the value ofisClientchanges.packages/synapse-interface/components/Pools/PoolHeader.tsx (4)
1-2: The
memofunction is imported from thereactlibrary to optimize thePoolHeadercomponent by avoiding unnecessary re-renders. This is a good practice for performance optimization.12-66: The
PoolHeadercomponent is now memoized using thememofunction from thereactlibrary. This is a good practice for performance optimization. However, ensure that the props passed to this component are either primitives or objects with stable identities to avoid unnecessary re-renders.13-14: The
PoolHeadercomponent now expectspoolandaddressas props. Ensure that all instances of this component throughout the codebase have been updated to pass these props.17-36: The
canDepositstate is memoized using theuseMemohook. This is a good practice for performance optimization. However, ensure that the dependencies of this hook are correctly specified in the dependency array.packages/synapse-interface/components/Pools/PoolCardBody.tsx (3)
1-4: The import statements are well-organized and necessary for the code to function correctly.
7-40: The
PoolCardBodycomponent is now memoized, which can help to avoid unnecessary re-renders and improve performance. The props are also properly typed, which can help to prevent bugs and improve code readability.1-45: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [42-84]
The
PoolTokenIconscomponent is now memoized, which can help to avoid unnecessary re-renders and improve performance. The props are also properly typed, which can help to prevent bugs and improve code readability.packages/synapse-interface/utils/actions/getPoolApyData.ts (4)
2-8: The import statements have been updated to reflect the changes in the function. Ensure that the imported modules and functions are available and correctly exported from their respective files.
48-63: The
readContractsfunction is now directly using thebalanceOfandtotalSupplyfunctions from theerc20ABIABI. This is a good optimization as it reduces the number of RPC calls. However, ensure that theerc20ABIABI includes these functions and that they return the expected results.67-71: The results from the
readContractsfunction are being assigned to variables. Ensure that the function returns the expected results in the correct order.73-74: The
synapsePerSecondvariable is being assigned a value from thesynapsePerSecondResultvariable or0nifsynapsePerSecondResultisnullorundefined. This is a good practice as it ensures thatsynapsePerSecondalways has a value.Overall, the changes in this file are well-structured and improve the performance of the
getPoolApyDatafunction. However, it's important to verify that the changes work as expected in the context of the entire application.packages/synapse-interface/contexts/UserProvider.tsx (6)
1-4: The import statements look fine. No issues found.
18-24: The new state variable
isClientis initialized correctly withuseState. TheisClientstate variable is used to control when data fetching and effects are executed, which can improve performance on the client side.44-46: This effect sets
isClienttotruewhen the component mounts. This is a common pattern for detecting whether code is running on the client side or server side in a Next.js application.48-54: This effect dispatches several actions to fetch price data when
isClientistrue. This ensures that these actions are only dispatched on the client side, which can improve performance.56-58: This effect dispatches the
setSwapChainIdaction whenchainis defined. This is a good practice as it ensures that thechain.idis always up-to-date in the Redux store.78-84: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [79-93]
This effect fetches and stores portfolio balances when
isClientistrueandaddressandchain.idare defined. It also resets the portfolio state whenaddressis not defined. This is a good practice as it ensures that the portfolio balances are always up-to-date in the Redux store and that the portfolio state is reset when the user disconnects their wallet.packages/synapse-interface/utils/actions/getPoolData.ts (4)
1-9: The import statements have been updated to reflect the new dependencies of the functions in this file. Ensure that these dependencies are correctly installed and imported.
18-94: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [10-20]
The function signature of
getBalanceDataremains the same. The function now usesmulticallto fetch all the data in a single RPC call, which is a good performance optimization.
118-123: The
getSinglePoolDatafunction now fetches theethPriceandavaxPricedirectly within its body, instead of relying ongetCorePoolData. This change reduces the number of RPC calls and improves performance.144-148: The
getSinglePoolDatafunction no longer includesvirtualPriceandswapFeein its return value. Ensure that this change does not break any code that relies on these properties.packages/synapse-interface/pages/pools/PoolCard.tsx (2)
18-31: The
PoolCardcomponent has been updated to use memoization. This is a good practice for performance optimization as it prevents unnecessary re-renders of the component. However, ensure that the props passed toPoolCardare not deeply nested objects or arrays, as React'smemoonly does a shallow comparison, and changes in properties of a nested object or elements of an array will not trigger a re-render.32-38: The
isClientstate variable is initialized tofalseand then set totruein auseEffecthook. This is a common pattern for preventing server-side rendering of client-side only logic, which can improve performance.
Summary by CodeRabbit
Refactor:
virtualPriceandswapFeeproperties, making them optional, providing flexibility in data handling.Bug Fix:
Please note that these changes are mostly under-the-hood improvements and may not result in noticeable changes in the user interface. However, they contribute to a more reliable and efficient application.
efd393a9907d5c20f203701a83b4cdc5ff8a988f: synapse-interface preview link
05ad7eb515ee2bf71fb647edada3f09fa6069bfc: synapse-interface preview link
6022fa5217d231fc23d936f3dd156bf31cdb95bf: synapse-interface preview link
adb0af519e58cbb389942a5685bebf15b7774551: synapse-interface preview link