Skip to content

v12.0.0 Cherry-Pick fix: Notifications platform links (#24708)#25214

Merged
hjetpoluru merged 1 commit intoVersion-v12.0.0from
v12.0.0/cherry-pick-7e6ab1d4a32699f218ea57292749b5262ee68592
Jun 12, 2024
Merged

v12.0.0 Cherry-Pick fix: Notifications platform links (#24708)#25214
hjetpoluru merged 1 commit intoVersion-v12.0.0from
v12.0.0/cherry-pick-7e6ab1d4a32699f218ea57292749b5262ee68592

Conversation

@matteoscurati
Copy link
Copy Markdown
Contributor

@matteoscurati matteoscurati commented Jun 11, 2024

Description

This PR introduces the logic to handle links within notifications to support the different platforms on which we can use the extension.

Original PR: #24708
This Cherry-Pick did not have any conflicts to resolve.

Open in GitHub Codespaces

Related issues

Fixes:

Manual testing steps

  1. Open the notifications list page
  2. Click on a product announcement
  3. Check the link in the detail page

Screenshots/Recordings

Before

After

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've completed the PR template to the best of my ability
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Description

Open in GitHub Codespaces

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

This PR introduces the logic to handle links within notifications to
support the different platforms on which we can use the extension.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24708?quickstart=1)

## **Related issues**

Fixes:

## **Manual testing steps**

1. Open the notifications list page
2. Click on a product announcement
3. Check the link in the detail page

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [x] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [x] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@github-actions
Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@matteoscurati matteoscurati marked this pull request as ready for review June 11, 2024 12:09
@matteoscurati matteoscurati requested review from a team as code owners June 11, 2024 12:09
@matteoscurati matteoscurati added the team-notifications-deprecated DEPRECATED: please use "team-assets" instead label Jun 11, 2024
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [788fc94]
Page Load Metrics (60 ± 8 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint6714091168
domContentLoaded9211231
load4411560168
domInteractive9211231
Bundle size diffs [🚨 Warning! Bundle size has increased!]
  • background: 22 Bytes (0.00%)
  • ui: 6.87 KiB (0.10%)
  • common: 3.38 KiB (0.05%)

@Prithpal-Sooriya Prithpal-Sooriya changed the title fix: Notifications platform links (#24708) fix: [v12] Notifications platform links (#24708) Jun 12, 2024
@Prithpal-Sooriya Prithpal-Sooriya changed the title fix: [v12] Notifications platform links (#24708) v12.0.0 Cherry-Pick fix: Notifications platform links (#24708) Jun 12, 2024
@hjetpoluru hjetpoluru merged commit b25d64e into Version-v12.0.0 Jun 12, 2024
@hjetpoluru hjetpoluru deleted the v12.0.0/cherry-pick-7e6ab1d4a32699f218ea57292749b5262ee68592 branch June 12, 2024 16:20
@github-actions github-actions bot locked and limited conversation to collaborators Jun 12, 2024
@metamaskbot metamaskbot added the release-12.0.0 Issue or pull request that will be included in release 12.0.0 label Jun 12, 2024
@metamaskbot
Copy link
Copy Markdown
Collaborator

No release label on PR. Adding release label release-12.0.0 on PR, as PR was cherry-picked in branch 12.0.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-12.0.0 Issue or pull request that will be included in release 12.0.0 team-notifications-deprecated DEPRECATED: please use "team-assets" instead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants