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

fix: do not warn about legacy capi in production #806

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

wattanx
Copy link
Collaborator

@wattanx wattanx commented Jun 12, 2023

πŸ”— Linked issue

Fixes: #805

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 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)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

The legacy capi message is for developers and users do not need to know this information, so it should not be displayed in production.

πŸ“ Checklist

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

@danielroe danielroe merged commit a6e6787 into nuxt:main Jun 12, 2023
@danielroe danielroe changed the title fix: output legacy capi warn only in dev mode fix: do not warn about legacy capi in production Jun 12, 2023
@wattanx wattanx deleted the issue-805-fix-capi-console-warn branch June 13, 2023 02:15
@danielroe danielroe mentioned this pull request Jun 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.

[bridge] [legacy capi] logs are displayed in the production environment.
2 participants