We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the new flat structure of components and two years of experience we no longer need to use the ambiguous communication name for the app.
communication
Rename the component to conversations. This name fits its job much better and also nicely complements the one picked for contacts.
conversations
contacts
Be sure to rename all class paths, code references and infrastructure code.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
With the new flat structure of components and two years of experience we no longer need to use the ambiguous
communication
name for the app.Describe the solution you'd like
Rename the component to
conversations
. This name fits its job much better and also nicely complements the one picked forcontacts
.Be sure to rename all class paths, code references and infrastructure code.
The text was updated successfully, but these errors were encountered: