No description
Find a file
2023-10-29 10:16:02 -04:00
public CSR-1390 add .hide to hide modal on load. 2023-10-29 10:16:02 -04:00
src Merge pull request #1461 from Safelite/feature/CSR-1384-modals-for-add-vaps 2023-10-27 16:58:25 -04:00
.gitattributes Add gitattributes file 2022-10-28 16:42:47 -04:00
.gitignore Added .gitignore for node_modules and other files 2021-09-21 08:34:57 -04:00
.prettierrc CSR-762 Edit prettier file 2022-10-12 13:46:18 -04:00
azure-pipelines.yml CSR-1392 2023-10-09 10:18:03 -04:00
babel.config.js Added back jest support for unit testing, added mock unit test 2021-10-27 11:24:32 -04:00
jest.config.js Minor treak and unit tests 2023-10-17 08:30:56 -04:00
package-lock.json Merge pull request #667 from Safelite/dependabot/npm_and_yarn/terser-4.8.1 2023-02-27 16:48:01 -05:00
package.json Add formatting before serve back 2022-10-28 11:06:14 -04:00
README.md Updated readme 2022-01-26 15:19:43 -05:00
vue.config.js remove calendar url from vue config 2023-10-20 19:51:09 +05:30
vue.release.config.js remove calendar url from vue config 2023-10-20 19:51:09 +05:30

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.