Skip to content

Conversation

@Barbapapazes
Copy link
Member

@Barbapapazes Barbapapazes commented Jan 31, 2024

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • πŸ“° Content (a new article or a change in the content folder)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

This is used to avoid to generate too many things reducing the generating time.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@Barbapapazes
Copy link
Member Author

can't be merged because of a Nuxt issue nuxt/nuxt#25535

@Barbapapazes
Copy link
Member Author

can't be merged because of a Nuxt issue nuxt/nuxt#25535

once resolved, we will be able to add more utm links to know where user come from.

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