Sushiswap.fi v1.2.0 feature epics:

Preface:

Currently sushiswap maintains various repos with different contributors who have different bandwidths, our refactor will aim to consolidate all repos under one infrastructure for better long term maintainability and to make addressing bugs or applying feature enhancements seamless for major engineering members. Our next step will be to reach feature parity across all repos and gradually deprecate sushiswapclassic instances. As part of consolidation we also aim to clean up our subgraph instances and produce a web3-sdk. This will also make it easier for contributors moving forward and reduce the current patchwork of different subgraph and web3 utility functions that are spread across different projects. All these steps will make it more feasible to rapidly add features to sushiswap without incurring increasing technical debt. Additionally this version will also address all table related issues and feedback we have consolidated over the past few weeks into a new layout with features that should enable easier harvest and better mobile support.

• Refactor

1. ✅ Modals global context for better accessibility, extension
2. ✅ Add scan wechat modal, dependent on (1)
3. ✅ Consolidate all components into one manageable Dashboard components file to reduce redundancy and code readability
   1. ✅ Smoke test feature parity with refactoring, currently missing:
      1. Current menu selection
4. Split forked components into services
   • lite: Margin
   • ✅ lite: one click Uni to SLP

• SushiswapJS npm module: @sushiswap/web3-sdk

1. ✅ Remove JS BigInt instances and notations (Safari doesn't like it when compiled)
2. ✅ export classes as modules
3. SushiswapJS Repo on github
4. publish to @sushiswap/web3-sdk

• Integrate all and consolidate all sushibar features

1. Dependant on @sushiswap/web3-sdk
2. ✅ Stake, Unstake xSUSHI (forked from classic)
3. Serve it up xSUSHI
4. ✅ Timelock (see below on the graph implementation)

• Improve table functionality

1. ✅ Better responsive layout - dynamic first column (smaller on mobile, should show 1 fixed column and 2 columns)
2. ✅ Sorting functionalities, even for web3 components that are loaded later on
3. ✅ Search filtering