PWA-3450 : Commit for initial package after conversion from TypeScrip…

[del15881]

…t to React

Description

This commit marks the Initial PWA LiveSearch Package, after conversion of the Referenced Repository (https://github.com/adobe/storefront-product-listing-page).

Currently It only has the feature to add Live Search Results to Category and Search Results Landing pages.

It currently is missing the Search Autocomplete AKA Search Popover feature.

The commit to work requires the Magento_LiveSearchGraphQlPwa module to be installed on Adobe Commerce Backend.
This module is currently available only for internal use.

Once installed the Live Search to be initialised on PLP and SRLP , it requires changes in local-intercept.js file of PWA Studio.

Example (local-intercept.js) :

`
const { Targetables } = require('@magento/pwa-buildpack');

function localIntercept(targets) {
const liveSearchTargetables = Targetables.using(targets);

//searchPage settings
const VeniaSearchPage = liveSearchTargetables.reactComponent(
    '@magento/venia-ui/lib/components/SearchPage/searchPage.js'
);

const LiveSearchPage = VeniaSearchPage.addImport(
    "import LiveSearchSRLPLoader from '@magento/venia-pwa-live-search/src/containers/LiveSearchSRLPLoader'"
);

VeniaSearchPage.insertBeforeJSX(
    'div className={classes.sidebar}',
    `<${LiveSearchPage} />`
);

VeniaSearchPage.removeJSX('div className={classes.sidebar}');
VeniaSearchPage.removeJSX('div className={classes.searchContent}');

//category page settings
const VeniaCategoryPage = liveSearchTargetables.reactComponent(
    '@magento/venia-ui/lib/RootComponents/Category/categoryContent.js'
);

const LiveCategoryContent = VeniaCategoryPage.addImport(
    "import LiveSearchPLPLoader from '@magento/venia-pwa-live-search/src/containers/LiveSearchPLPLoader'"
);

VeniaCategoryPage.insertBeforeJSX(
    '<Breadcrumbs categoryId={categoryId} />',
    `<${LiveCategoryContent} categoryId={categoryId} />`
);

VeniaCategoryPage.removeJSX('<Breadcrumbs categoryId={categoryId} />');
VeniaCategoryPage.removeJSX('<StoreTitle />');
VeniaCategoryPage.removeJSX('article className={classes.root}');

}

module.exports = localIntercept;

`

Related Issue

https://jira.corp.adobe.com/browse/PWA-3450

Closes #PWA-3450.

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

• I have added tests to cover my changes, if necessary.
• I have added translations for new strings, if necessary.
• I have updated the documentation accordingly, if necessary.

[pwa-studio-bot]

	Messages
📖	Associated JIRA tickets: PWA-3450.
📖	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).
📖	Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.

Generated by 🚫 dangerJS against 4a4552c

[pwa-studio-bot]

	Fails
🚫	node failed.

Log

ERROR ON TASK: cypressTests

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

Generated by 🚫 dangerJS against 4a4552c

[pwa-studio-bot]

	Fails
🚫	node failed.
🚫	Cypress tests in the following files did not pass 😔. All tests must pass before this PR can be merged contains valid CMS Page data: CypressError: `cy.visit()` failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false displays subcategories from the default root category: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false displays assigned products: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false ,contains valid CMS Page data specific to the different store: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false shows categories specific to the different store: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false shows products specific to the categories in the different store: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false ,lets users add products to cart regardless of store view: CypressError: cy.visit() failed trying to load: https://pr-4462.pwa-venia.com/ The response we received from your web server was: 504: Gateway Timeout This was considered a failure because the status code was not 2xx. If you do not want status codes to cause failures pass the option: failOnStatusCode: false

Log

ERROR ON TASK: cypressTests

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

Generated by 🚫 dangerJS against 4a4552c

[glo80684]

Hey team,
I'm closing and reopening this PR #4462 so that it picks up the updated resources.
The current workflow is still tied to the old AMI, and reopening should help trigger a fresh build with the latest configuration.
Thanks!

[glo82145]

run pr-test

[pwa-test-bot]

Successfully started codebuild job for pr-test