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

docs: Improve performance guide with channel context usage warning #2043

Merged
merged 3 commits into from
Apr 6, 2023

Conversation

vanGalilea
Copy link
Contributor

🎯 Goal

Improve performance guide with channel context usage warning when used within message level customized components.

🛠 Implementation details

Describing the needed information with regards to the usage of the channel context

🎨 UI Changes

N/A

🧪 Testing

N/A

☑️ Checklist

  • I have signed the Stream CLA (required)
  • PR targets the develop branch
  • Documentation is updated
  • New code is tested in main example apps, including all possible scenarios
    • SampleApp iOS and Android
    • Expo iOS and Android

@vanGalilea vanGalilea changed the title Improve performance guide with channel context usage warning docs: Improve performance guide with channel context usage warning Apr 5, 2023
@sonarcloud
Copy link

sonarcloud bot commented Apr 6, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@vanGalilea vanGalilea merged commit 40bc4bf into develop Apr 6, 2023
@vanGalilea vanGalilea deleted the docs/performance-guide-context-addition branch April 6, 2023 08:46
@stream-ci-bot
Copy link
Contributor

🎉 This PR is included in version 5.13.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants