magento / pwa-studio

🛠Development tools to build, optimize and deploy Progressive Web Applications for Magento 2.
https://developer.adobe.com/commerce/pwa-studio/
Open Software License 3.0
1.06k stars 683 forks source link

QA/dev user should not required to input html suffix in front end for… #4290

Open glo11372 opened 1 month ago

glo11372 commented 1 month ago

… loading page

Description

1.Open venia and click any category then go to PDP page, it will open .html in URL

Related Issue

Closes #https://jira.corp.adobe.com/browse/PWA-3291

Acceptance

Verification Stakeholders

Specification

Verification Steps

Test scenario(s) for direct fix/feature

Test scenario(s) for any existing impacted features/areas

Test scenario(s) for any Magento Backend Supported Configurations

Is Browser/Device testing needed?

Any ad-hoc/edge case scenarios that need to be considered?

Screenshots / Screen Captures (if appropriate)

Breaking Changes (if any)

Checklist

pwa-studio-bot commented 1 month ago
Fails
:no_entry_sign: `node` failed.
:no_entry_sign: Unit tests in the following files did _not_ pass 😔. All tests must pass before this PR can be merged
  • packages/peregrine/lib/talons/Gallery/__tests__/useGallery.spec.js
Messages
:book: Associated JIRA tickets: [PWA-3291](https://jira.corp.magento.com/browse/PWA-3291).
:book: DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
:book: Access a deployed version of this PR [here](https://pr-4290.pwa-venia.com/). Make sure to wait for the "pwa-pull-request-deploy" job to complete.

Log

ERROR ON TASK: unitTests


Error:  Danger had errors running. See message(s) above for more details.
danger-results://tmp/danger-results.json

Generated by :no_entry_sign: dangerJS against 13c20cfd09082b1316cc8b9b6b00f85fb3595758