Skip to content

feat: disable analytics#174

Closed
Baroshem wants to merge 1 commit intochore/2.5.0from
feat/disable-analytics
Closed

feat: disable analytics#174
Baroshem wants to merge 1 commit intochore/2.5.0from
feat/disable-analytics

Conversation

@Baroshem
Copy link
Copy Markdown
Collaborator

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes (if not applicable, please state why)

},
}

if (useRuntimeConfig().public.cloudinary.analytics) {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

these analytics need to be on by default

colbyfayock added a commit to cloudinary-community/cloudinary-util that referenced this pull request Dec 14, 2023
# Description

Updates the construct URL function to work properly when analytics is
disabled.

Previous, passing the config.url.analytics as false would work, but not
the analytics function option.

This normalizes behavior and makes sure it works as expected

## Issue Ticket Number

Helps to address issue found:
nuxt-modules/cloudinary#174

<!-- Specify above which issue this fixes by referencing the issue
number (`#<ISSUE_NUMBER>`) or issue URL. -->
<!-- Example: Fixes
https://github.com/colbyfayock/cloudinary-util/issues/<ISSUE_NUMBER> -->

## Type of change

<!-- Please select all options that are applicable. -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Fix or improve the documentation
- [ ] This change requires a documentation update


# Checklist

<!-- These must all be followed and checked. -->

- [ ] I have followed the contributing guidelines of this project as
mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md)
- [ ] I have created an
[issue](https://github.com/colbyfayock/cloudinary-util/issues) ticket
for this PR
- [ ] I have checked to ensure there aren't other open [Pull
Requests](https://github.com/colbyfayock/cloudinary-util/pulls) for the
same update/change?
- [ ] I have performed a self-review of my own code
- [ ] I have run tests locally to ensure they all pass
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes needed to the documentation
@Baroshem
Copy link
Copy Markdown
Collaborator Author

Closing in favor of #173

@Baroshem Baroshem closed this Dec 20, 2023
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