-
Notifications
You must be signed in to change notification settings - Fork 119
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
Discussion create #229
Discussion create #229
Conversation
Codecov Report
@@ Coverage Diff @@
## master #229 +/- ##
=========================================
- Coverage 53.81% 53.5% -0.32%
=========================================
Files 70 70
Lines 2568 2583 +15
Branches 380 380
=========================================
Hits 1382 1382
- Misses 1186 1201 +15
Continue to review full report at Codecov.
|
The current implementation allows a discussion to be created without a parent/origin message in the parent room. Is this something we'd like to allow? @marceloschmidt @ggazzo @sampaiodiego |
Now that you mentioned, it doesn't seem to make much sense. |
Though, do we have this type of logic here? |
@marceloschmidt The API as it is allows that to happen as much as the implementation on the Rocket.Chat side, so if we want to change something, we're gonna have to change in both places 😛 I think the best thing we could do here for the developer is to provide a The only problem is... where do we put it? In the |
on Rocket.Chat side we have a createDiscussion method that handles everything, you can provide either a
an API like this makes more sense to me 👍 |
Oooh, I've recently come to realize that a message is always created along with a discussion, even if the user clicks on the I might be able to give this a try today |
@d-gubert did you manage to do it? |
I'm closing this one in favor of a different branch with the proposed approach. |
What? ⛵
Why? 🤔
This will allow us to create discussions via apps.