App: next release #638
Draft
App: next release #638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Subgraph: reorganize the operations handling + fix the leverage detection - openLeveragePosition tx flow: don’t store the leverage mode in storage (rely on the subgraph instead)
A new DEPLOYMENT_FLAVOR the env var can be set to a string, which gets displayed in the top bar.
This aims to unify the price fetching strategy with the rest of the data fetching hooks, by relying on TanStack Query rather than using an internal provider. - Support setting a CoinGecko API key (demo or pro). - Refactor usePrice() and its callers to return UseQueryResult. - Remove the <Price> provider (relying on the TanStack Query cache instead). - Remove the possibility to update prices in demo mode (UpdatePrices.tsx). - Remove the random price variations in demo mode. - Move PRICE_REFRESH_INTERVAL into constants.ts.
* ErrorBox: animate chevron * Transaction screen: better ErrorBox transitions * Tx Flow: show errors thrown by writeContractParams() in the UI
- The closing panel doesn’t show “you repay with” anymore in this situation. - The content of the info message and the submit button are now based on being in claimOnly mode or not. - Moved the submit button label into content.tsx. - On the tx flow, “you repay” doesn’t appear if 0. - writeContractParams() only fails if closeLoanPosition === null (was !closeLoanPosition before, which was including 0n).
A fully redeemed loan is determined from the combination of a redeemed status (see subgraph to know how this is determined) and a debt of 0. In this mode, the loan card only shows three values: the collateral (or net value in leverage mode), the interest rate, and the redemption risk. The three others will only get displayed if the loan debts goes above 0 again.
- Use a single useQuery() for the two requests - useCheckLeverageSlippage() now takes collIndex a parameter rather than a loan object - Move useCheckLeverageSlippage() to liquity-leverage.ts
Also: - Remove Footer.tsx - Move the React Query client into its own service - Various related changes - Align the LoanScreenCard copy animation with the about modal
…cts (#646) This has been removed from recent versions of the manifest and is not needed by the app.
* Add anim-utils * On the transaction screen card, do not wait for loan details when closing a loan
- Onchain blocking list - VPN & country block via vpnapi.io
- Update ABI - Remove unused properties from the schema - AssemblyScript fixes
We can do this now that Governance is a submodule of the repo.
--------- Co-authored-by: Pierre Bertet <[email protected]>
Also: - Staking through governance - EIP 2612 Permit support - AnchorTextButton: fix className inheritance - Add missing env vars to .env - Fetch initiatives from subgraph - Publish known initiatives with the app - Env: add KNOWN_INITIATIVES_URL - useInitiatives() + useKnownInitiatives() - Update graphql files
Add state needed for calculating voting power to subgraph
App: show live voting power
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR can be used to keep track of the changes coming in the next release, and will be merged into main for each release.