Skip to content
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

feat: catalogue can use google analytics #4473

Merged
merged 6 commits into from
Nov 13, 2024
Merged

Conversation

connoratrug
Copy link
Contributor

@connoratrug connoratrug commented Nov 11, 2024

What are the main changes you did:

  • add option to configure google analytics

See: https://github.com/orgs/molgenis/projects/15/views/1?sliceBy%5Bvalue%5D=Dev&pane=issue&itemId=79942482&issue=molgenis%7CGCC%7C648

how to test:

  • is a accept / localhost context configure google analytics and check if analytics are sent then analytics is setup and user accepts the cookies.

todo:

  • updated docs in case of new feature
  • added/updated tests
  • added/updated testplan to include a test for this fix, including ref to bug using # notation

Add option to choose analytics provider ( siteimprove or googlegoogle-analytics)
Analytics key can still be set via NUXT_PUBLIC_ANALYTICS_KEY env var
Provider can be set via NUXT_PUBLIC_ANALYTICS_PROVIDER env var
apps/nuxt3-ssr/app.vue Outdated Show resolved Hide resolved
apps/nuxt3-ssr/Dockerfile Outdated Show resolved Hide resolved
@@ -109,3 +109,10 @@ The label shown on landing CTA element for each of the main sections

A Themed favicon is set by placing a [theme].icon file in the public/img folder. At runtime the [theme] is replaced by the value as set in ```NUXT_PUBLIC_EMX2_THEME``` environment setting. If no theme is set, the default molgenis favicon is show.

## Analytics

Analytics can be enabled by setting the following environment variables:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can I also set this via the user interface?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i thought about that, but has several implication for ssr render speed ( if it could change at any time , is always needs to checked in the db ) , would suggest to keep as it, evaluatie this setup ( i suspect not not need to change this often ) , also having these kinds of things injected from the environment has the benefit of being able to move the project/db around while having different configs for acc, prod, ...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link

sonarcloud bot commented Nov 11, 2024

@mswertz mswertz changed the title Feat/catalgue analytics feat: catalogue can use google analytics Nov 12, 2024
Copy link
Member

@mswertz mswertz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets try it :-)

@connoratrug connoratrug merged commit 18d654b into master Nov 13, 2024
6 checks passed
@connoratrug connoratrug deleted the feat/catalgue-analytics branch November 13, 2024 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants