78ad9c7983e235ed3504ee4c7e6272ba GitDocument docs/guides/angular-component-development.md intershop/intershop-pwa develop • is supposed to be handled by methods of services. See also Angular Style Guide. Put as Little Logic Into constructor as Possible - Use ngOnInit See The • dynamically to attributes or properties: interpolation or property binding. In the PWA we prefer using property binding since this covers more cases in the same

kb_sync_latest_only daae6d0cd7d89eb22f3be9c57524a7a0 GitDocument docs/guides/eslint.md intershop/intershop-pwa develop • The PWA uses ESLint for static code analysis and to enforce best practices. In order to use ESLint with Angular, we use the typescript-eslint and angular-eslint • angular-eslint packages extensively. The PWA's ruleset is configured in .eslintrc.json and includes base rulesets to extend from, plugins with additional rules

via docker-compose.yml configuration: pwa: environment: - FEATURES=tracking - GTM_TOKEN=GTM-ABCDEFG Example via PWA Helm Chart: environment: - name: FEATURES • a1e1b05efbe2cb50ed9988bf5d2c8a1b GitDocument docs/guides/google-tag-manager.md intershop/intershop-pwa develop • Manager, the popular library Angulartics2 is used. Note The standard Intershop PWA Google Tag Manager integration is very basic and currently only supports the

0b217fb09057296d1da3c1eb6a726467 GitDocument docs/guides/angular-change-detection.md intershop/intershop-pwa develop • do not expect any async tasks to finish in the near future. The Intershop PWA effectively uses this concept for communication with the CMS Design View.

0deab000f0954b5960e5a31248544744 GitDocument docs/guides/state-management.md intershop/intershop-pwa develop

This guide describes how to propagate additional configuration from the outside into the PWA client application to be used on the storefront. Configuration • 010f4228be9a7b1d1eb65cd10098ae23 GitDocument docs/guides/propagating-environment-variables.md intershop/intershop-pwa develop • handling basically uses this method of configuration to dynamically provision a PWA server-side rendering run for a specific channel. Currently all of those properties

scrape_configs: - job_name: 'pwa-nginx' scrape_interval: 5s dns_sd_configs: - names: - 'tasks.pwa-nginx' type: 'A' port: 9113 - job_name: 'pwa-ssr' scrape_interval: • 371cea2e77a87852c6b765a103b0d584 GitDocument docs/guides/prometheus-monitoring.md intershop/intershop-pwa develop • The PWA can be monitored using Prometheus. Activating the feature Prometheus for the nginx or SSR container exposes metrics on port 9113 on the /metrics

b9ec180b0884de2b78f6b70623a42f12 GitDocument docs/guides/data-handling-with-mappers.md intershop/intershop-pwa develop • communicating with the Intershop REST API should only respond with mapped PWA models. The format of raw data from the server is defined by an interface

adc6783d5931b1fc273945f7b5c248ac GitDocument docs/guides/mocking-rest-calls.md intershop/intershop-pwa develop • new features in parallel where backend and frontend are involved. In the PWA we supply a mocking mechanism so the frontend team can start implementation • configuration example will mock all CMS calls. apiMockPaths: ['^cms/.*'], Tip With PWA version 5.2.0 a filtering for matrix parameters (e.g. /cms;pgid=JdbSDW8rr

kb_sync_latest_only fa4ddf969e8600999c34ba735dd94d86 GitDocument docs/guides/testing-jest.md intershop/intershop-pwa develop

your interest in contributing to our open source software project ("project PWA storefront" or just "project") made available by Intershop Communications • submitted, in any form and in any manner, to ISH in respect of the project PWA storefront (collectively "Contributions"). With your click on the button you • hereby grant to contribute your works and developments with respect to ISH PWA storefront project. You hereby grant, and agree to grant, to ISH non-exclusive

2ddd07a3eae8c752987aed379e6dcd2e GitDocument docs/guides/icm-http-error-mapping.md intershop/intershop-pwa develop • localized messages in the body of an error is being implemented. For the PWA this means that potentially every service and component managing a different • different resource has to handle different formats. In version 0.23 of the PWA we refactored the error handling to provide a consistent simplified format for

c6afa7f39139d35c69f6d1fedb79c8c0 GitDocument docs/guides/newsletter-subscription.md intershop/intershop-pwa develop • Introduction In the PWA registered users can subscribe to and unsubscribe from a newsletter service. Configuration To enable this feature, an e-mail marketing • Intershop Commerce Management under Channel Preferences | E-mail Marketing. The PWA receives information about the e-mail provider configuration via the /configurations

"<addressDoctor-password>", "maxResultCount": "5" }' For the current PWA Helm Chart that is also used in the PWA Flux deployments, the Address Doctor configuration looks • the address doctor the PWA needs to render the <ish-lazy-address-doctor> component. When the user submits the address data, the PWA needs to send a feature • kb_sync_latest_only 7f442652fbdd9f1e3bd1c394c00967c2 GitDocument docs/guides/address-doctor.md intershop/intershop-pwa develop

b20489ae1bcedae2edeacd9165ccddd7 GitDocument docs/guides/authentication_icm.md intershop/intershop-pwa develop • be renewed. Hence, the token will not expire as long as the user keeps the PWA open in the browser. Logout When the user logs out by clicking the logout • service in order to deactivate the token on server side. Besides this, the PWA removes the token on browser side, fetches a new anonymous user token, and

behavior may be reported to the community leaders responsible for enforcement at pwa@intershop.de or by contacting one or more of the project maintainers. All • dda5604e3c9d2fe226ab25a1ac5194e2 GitDocument CODE_OF_CONDUCT.md intershop/intershop-pwa develop

encountering a configurable product, the PWA directs to the configuration page, where the product can be composed. The PWA supports committing and un-committing • 40895d3c80f53e30bfb1adcba17c4e18 GitDocument docs/guides/tacton-product-configuration.md intershop/intershop-pwa develop • integrated Tacton CPQ for handling complex product configuration scenarios. The PWA uses the self-service API to interactively configure a product and submit

properties are not overridden. Multiple PWA channels can be set up by supplying a YAML configuration listing all domains the PWA should work for. For more information • should be used. For that reason, also the PWA Helm chart does not support deploying an own Redis service with the PWA. Only the redis.uri can be configured • kb_sync_latest_only d54953681285c76a86208bec053d8961 GitDocument docs/guides/nginx-startup.md intershop/intershop-pwa develop

Approach Concept - Logging Guide - Themes Guide - Client-Side Error Monitoring with Sentry Guide - Google Tag Manager Guide - Monitoring with Prometheus • build the Intershop PWA in server-side rendering mode, you can use the package.json script npm run build , which builds the Intershop PWA with the production • configurations of the PWA is entirely done by environment variables. This approach was chosen to have the best possible compatibility when running the PWA either from

.+: - path: /punchout type: Punchout For the current PWA Helm Chart that is also used in the PWA Flux deployments, the same punchout configuration would • ICM configured PWA deployment /punchout route. Registration There is currently no possibility to register a new punchout user in the PWA. Token Lifetime • 10b539e3bae2ba717d70d7ab7329d807 GitDocument docs/guides/authentication_punchout.md intershop/intershop-pwa develop