Closed Platonn closed 5 years ago
Implementation of simple configurable routes mechanims is already merged into develop for some time.
So I moved out to #564 the acceptance criteria: 'Replace all hardcoded URLs with usages of configurable routes mechanism', which is not merged yet
Sections:
Created a follow-up ticket to take care of documentation: GH-742. Moving this ticket now to QA.
It's subtask of #3
This ticket covers only simple configuration mechanism. The config should be provided statically (without getting routes config via http yet - there is other ticket for that).
Acceptance criteria:
:productCode/product/:campaignName/:productName
(though only :productCode parameter is mandatory, other parameters are only for SEO) and have also a urlproducts/:productCode
product
entity has a propertycode
, but urls make use of:productCode
name)After all many unit/e2e tests should be fixed then, for sure those which:
routerLink='/hardcoded-url'
router.navigate()
,routerService.go()
(our facade) or dispatching the actiongo
❓ Maybe it would be good to have another big happy path e2e tests for using translated routes?