Skip to content

feat: add estimated yield view#2695

Draft
mmioana wants to merge 3 commits intodevelopfrom
feat/JUM-520-estimated-yield
Draft

feat: add estimated yield view#2695
mmioana wants to merge 3 commits intodevelopfrom
feat/JUM-520-estimated-yield

Conversation

@mmioana
Copy link
Copy Markdown
Contributor

@mmioana mmioana commented Feb 12, 2026

Which Jira task belongs to this PR?

Contributes to https://lifi.atlassian.net/browse/JUM-520
Closes https://linear.app/lifi-linear/issue/JUM-591/estimated-yield-connect-yield-estimation-to-the-earn-action-section

Why did I implement it this way?

Checklist before requesting a review

  • I have performed a self-review of my code
  • This pull request is as small as possible and only tackles one problem
  • I have added tests that cover the functionality / test the bug
  • If this changed the API, I have updated the documentation
  • I have provided QA instructions for the feature / fix implemented in this PR (if applicable)
  • I have provided instructions for any environment / deployment changes that this PR needs when merged

@mmioana mmioana self-assigned this Feb 12, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
jumper-exchange Ready Ready Preview, Comment Apr 28, 2026 3:25pm
jumper-exchange-storybook Ready Ready Preview, Comment Apr 28, 2026 3:25pm

Request Review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 12, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 44c7778c-39fe-488b-881e-1c635937ede4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/JUM-520-estimated-yield

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 12, 2026

✅ All snapshot tests passed

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 12, 2026

Playwright test results

passed  54 passed
flaky  2 flaky
skipped  1 skipped

Details

stats  57 tests across 11 suites
duration  4 minutes, 20 seconds
commit  8772d99

Flaky tests

chromium › mainMenu.spec.ts › Main Menu flows › Should open Github page inside Resources section (Qase ID: 15)
chromium › settings.spec.ts › Settings menu [Viewport: Mobile] › Should verify all settings menu functionality (Qase ID: 7)

Skipped tests

chromium › themeManipulation.spec.ts › Switch between dark and light theme and check the background color › Partner theme should appear in theme menu and apply background color (Qase ID: 49)

📋 View Detailed Qase Report

@mmioana mmioana force-pushed the feat/JUM-520-request-redeem-flow branch from a0341d1 to bbe848c Compare February 20, 2026 13:47
@mmioana mmioana force-pushed the feat/JUM-520-request-redeem-flow branch from 5f36e54 to df577d3 Compare March 5, 2026 08:27
@mmioana mmioana force-pushed the feat/JUM-520-estimated-yield branch from 3c1ab02 to 23dfd49 Compare March 5, 2026 08:47
@mmioana mmioana force-pushed the feat/JUM-520-request-redeem-flow branch 5 times, most recently from b846151 to 5e2530e Compare March 13, 2026 09:57
@mmioana mmioana force-pushed the feat/JUM-520-request-redeem-flow branch 2 times, most recently from 9c84f0d to ff7214f Compare March 23, 2026 09:09
Base automatically changed from feat/JUM-520-request-redeem-flow to develop March 23, 2026 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant