-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap proposals #50
Comments
We should also see how we can extract deeper navigation paths (more than 2 levels) in GA. Currently, we're able to get
|
One more thing which I'm experimenting with is a parser which empowers partial evaluation with prepack. This will allow us to collect metadata from a broader range of apps. |
We also need to support setting the oauth2 token as an env variable as most gatsby sites are built in a CI environment. |
@KyleAMathews I'll open a PR with this right after we merge this. What do you think about: GuessPlugin({
GA: 'XXXXXX',
token: JSON.parse(require('./credentials.json')),
...
}) If |
I've heard folks are also interested in a demonstration of how Guess can be used with either service workers or service worker libraries such as Workbox. In an app where you may already be using service workers to precache/prefetch or fully using PRPL, having a clear story there would be nice. I actually think we're not a million miles away from explaining this through Gatsby. As mentioned in another issue, I think there's a story in using our predictions to just fetch data/JSON for routes that may not be clear to folks today. |
I think we can close the issue for now, we have descent part of the roadmap already in. |
Roadmap/Ideas
Features / Ease of use
Code-sharing
Machine Learning
Community
Integrations
Any other ideas we want to consider? @mgechev @khempenius @KyleAMathews @MarkEdmondson1234
The text was updated successfully, but these errors were encountered: