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: document incident actions #6396

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Lulalaby
Copy link
Contributor

@Lulalaby Lulalaby commented Sep 1, 2023

Waiting for #7098

@sebm253 sebm253 mentioned this pull request Sep 1, 2023
2 tasks
DonovanDMC added a commit to OceanicJS/Oceanic that referenced this pull request Sep 3, 2023
@Lulalaby Lulalaby marked this pull request as ready for review September 12, 2023 23:56
docs/resources/Guild.md Outdated Show resolved Hide resolved
docs/resources/Guild.md Outdated Show resolved Hide resolved
docs/resources/Guild.md Show resolved Hide resolved
docs/resources/Guild.md Outdated Show resolved Hide resolved
docs/resources/Guild.md Outdated Show resolved Hide resolved
docs/resources/Guild.md Show resolved Hide resolved
@Soheab
Copy link

Soheab commented Oct 1, 2023

Does this fire any gateway event like GUILD_UPDATE when the actions change at any time? Doesn't seem like it.

@Soheab
Copy link

Soheab commented Oct 3, 2023

Passing null to any of the fields disables all actions, is this intended?

Edit: when only one field is being set.

@Lulalaby
Copy link
Contributor Author

Lulalaby commented Oct 3, 2023

It wasn't the previous behavior at least

@seailz
Copy link
Contributor

seailz commented Dec 1, 2023

any update on this one?

@sdanialraza
Copy link
Contributor

There also seems to be dm_spam_detected_at and raid_detected_at fields, could you please document those as well?

@bsian03 bsian03 mentioned this pull request Feb 27, 2024
54 tasks
@Lulalaby Lulalaby closed this Apr 25, 2024
@Lulalaby Lulalaby deleted the incident-actions branch April 25, 2024 10:47
@Lulalaby Lulalaby restored the incident-actions branch April 25, 2024 10:48
@Lulalaby Lulalaby reopened this Apr 25, 2024
@Lulalaby
Copy link
Contributor Author

@sdanialraza i added the fields to the documentation as well

@Lulalaby Lulalaby changed the title Document incident actions docs: document incident actions Apr 25, 2024
@JustinBeckwith JustinBeckwith self-requested a review May 27, 2024 02:23
@JustinBeckwith
Copy link
Contributor

Note for future me - this is currently flagged as private in our Open API spec, and I need to go figure out why.

@Lulalaby
Copy link
Contributor Author

yeah heard that. surprises me

@Lulalaby
Copy link
Contributor Author

Lulalaby commented Aug 24, 2024

I'll have to redo the pr if #7098 is merged, something messed up

Comment on lines +668 to +673
```json
{
"invites_disabled_until": "2023-09-01T14:48:02.222000+00:00",
"dms_disabled_until": null
}
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either the example is incomplete or dm_spam_detected_at and raid_detected_at should be marked as optional in the above table.

###### JSON Params

> info
> Both `invites_disabled_until` and `dms_disabled_until` can be disabled for a maximal timespan of 24 hours in the future.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> Both `invites_disabled_until` and `dms_disabled_until` can be disabled for a maximal timespan of 24 hours in the future.
> Both `invites_disabled_until` and `dms_disabled_until` can be enabled for a maximal timespan of 24 hours in the future.

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.

7 participants