No description
Find a file
2025-08-29 10:00:01 -04:00
playwright-tests Comment to rerun 2025-08-04 16:13:35 -04:00
public CASH-1403: Payment parity changes 2025-08-26 14:58:51 -04:00
src CASH-1403: Parity - increase height for error messages 2025-08-29 10:00:01 -04:00
temp Rerun after agent disk space failure 2025-07-15 12:22:46 -04:00
.gitattributes Add gitattributes file 2022-10-28 16:42:47 -04:00
.gitignore Removes Playwright testing setup from core project 2025-06-05 16:22:34 -04:00
.prettierrc CASH-256 2025-02-14 15:13:26 -05:00
azure-pipelines-automated-testing.yml Changes pipeline pool to AmazonLinuxPool 2025-07-22 10:28:23 -04:00
azure-pipelines.yml new tag to devops template that does workspace cleanup 2025-08-20 10:44:12 -04:00
babel.config.js Added back jest support for unit testing, added mock unit test 2021-10-27 11:24:32 -04:00
Dockerfile.playwright Loads environment variables in Docker containers 2025-07-15 11:29:49 -04:00
jest.config.js CASH-1048 fix unit test. 2025-07-30 16:05:21 -04:00
package-lock.json using develops package-lock.json 2025-07-09 09:47:04 -04:00
package.json Adding test:unit script for pipeline run 2025-07-10 11:46:02 -04:00
README.md Updated readme 2022-01-26 15:19:43 -05:00
vue.config.js BRM remove temp file. 2025-08-14 08:07:18 -04:00
vue.release.config.js CASH-109 2025-01-18 08:37:20 -05:00

Fix My Glass Vue Project


This Repository is for Fix My Glass front end Vue and documentation associated with it.

Routing

We are using Vue Router 4.x for our front end routing. We are using a runtime dynamic routing solution. Some more information about dynamic routing can be found on the official Vue Router documentation.

Next() - Is a function that is native to Vue Router in which we call in order to send the user where want them to go based on some logic we have. You can read more about Navigation Guards and the Next() function on the Vue Router documentation.

GetRouteInfoFromPageName(PageName) - This method typically takes the query string value of fmgPage and passes it into a call to our Content Service. The service will pull information on the page; matching page name passed to page name in our Cms. If we have a match, we will compile the route information and send it to our router to process. If we do not have a that page in our Cms, the user will be served back a 404 page while retaining the structure.

GoToFunnelStartOn404(next) - When a user tries to go to a page that doesn't exist in the CMS, they will be put back to the 'Start' of the funnel which is whatever page is marked as the homepage on Sitefinity.