-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Document polls. #6746
Document polls. #6746
Conversation
Probably should mention answers limit (10 answers per poll) |
Can guilds with |
Should be done now. |
it seems like this version of the documentation is missing the |
Thank you, works! |
Create a seperate permission node so the communities we are in won't just spam a gazillion polls? |
Is it intended that |
No. Thanks for catching this. Might be a little while until we fix this though as we're heading into the weekend. :( |
docs/resources/Poll.md
Outdated
| expiry | IS08601 timestamp | The time when the poll ends. | | ||
| allow_multiselect | boolean | Whether a user can select multiple answers | | ||
| layout_type | integer | The [layout type](#DOCS_RESOURCES_POLL/layout-type) of the poll | | ||
| results | [Poll Results Object](#DOCS_RESOURCES_POLL/poll-results-object-poll-results-object-structure) | The results of the poll | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
results
seems to be nullable only for messages received over a gateway connection, I've yet to see it null over rest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our intention is that it should be always non-null (with just... default values for polls without votes yet). Are you still seeing it null through the Gateway? I'm going to check later just wondering if anyone knows right now. :P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're unlikely to support this. :( If you need to manually end your polls, create a bot so it can own the polls. |
Another question: Would it be possible to re-open polls ( Via API or otherwise ) ? For instance, when they expire after a week |
Discord has announced a Create Polls permission or similar, they are going to be documented, right? 😅 |
No, polls closing is a final state.
Yes. |
This endpoint will start including both reactions and poll results. But actually I've been thinking about my decision in #6746 (comment) and I actually think it's better for the future if |
Done: These are things that should have some semblence of stability. * Document model * Document gateway events * Document endpoints. * Abort errors.
In case you missed it, this newest update to the docs includes the I believe that I have resolved all outstanding issues. If nothing bad comes up, this PR will be merged by EOD. |
Does a poll naturally "expiring" also fire a |
I believe it does from what I have seen myself (to be clear, I don't work for Discord so I don't know for certain). |
Yes, specifically it is sent right now when the poll finishes counting the votes. :) |
Final issue i've found, sending content and embeds with polls works fine but it seems attachments collide with undocumented poll features; could this be disabled for now, or are we meant to implement compatibility...? |
Yes, there was |
For now you're not able to have |
I said EOD but got distracted. :P |
Will there be an addition to the change log with information about this new feature in the future? |
@Lulalaby I think you're saying that the message returned from the Please note that |
yeah, thank you |
Anyone able to reproduce |
Summary
Polls!
Hey folks, Discord plans to add first-party support for polls. The feature has started it's old good experimentation phase today, so now's about the time to document it as well. We expect that bots will be able to create these first-party polls when they become available. As usual this is subject to change yadda yadda no guarentees yadda yadda, but I personally I don't expect any changes.
However... some things are still being implemented right now for bots:
content
,components
and a variety of other fields are not able to be sent alongside thepoll
field.poll
right now either. You won't be able to edit a poll's data anyways in the future for now, but you will be able to edit everything else (likecontent
) after (2) is done.Most of this stuff will be done next week, after people are back from GDC. :)
Anyways cheers. I probably got some stuff wrong in this documentation so I look forward to the online community telling me that :)