# Log

## To Do

- The build will need to have an export as an entry point so that we can call functions and variables from within GTM. This will allow us to proxy variable functions through GTM for anything that relies on the variable but cannot be removed from GTM into this project.
- `./src/variables/pagePathAndHash.js` has been refactored from using GTM-built-in variables, we will need to verify it works properly.
  - `./src/variables/newHistoryFragment.js` See notes in file.

### Needs Implementation

- `./src/variables/clickHostname.js`
- `./src/variables/clickElement.js`

### Globals Needed

These either need code written for them or the linter needs to know they exist. This may depend on how much we can port.

- ga
- window.dataLayer

## Questions

- Not sure if we want to contain all the variables in a single export, or if we keep them all as separate files.
  - We could wrap them into `variables.js` that just imports and exports them as a single `module.exports`
  - This gives us the benefit of being able to import many via `import { var1, var2, var3 } from 'variables';` Rather than across multiple lines that are redundant/verbose.