[Snipy7374]

Summary

• Closes Implement new content scan flags #1628

Checklist

• If code changes were made, then they have been tested
  • I have updated the documentation to reflect the changes
  • I have formatted the code properly by running uv run nox -s lint
  • I have type-checked the code by running uv run nox -s pyright
• This PR fixes an issue
• This PR adds something new (e.g. new method or parameters)
• This PR is a breaking change (e.g. methods or parameters removed/renamed)
• This PR is not a code change (e.g. documentation, README, ...)

[read-the-docs-community]

Documentation build overview

📚 disnake | 🛠️ Build #35844828 | 📁 Comparing 7810653 against latest (def5844)

  🔍 Preview build  

4 files changed

± genindex.html
± whats_new.html
± api/components.html
± api/messages.html

[shiftinv]

Not really a fan of this naming, but then again, UnfurledMediaItemContentScanMetadata would be... a lot :>
While the API docs group this object under the unfurled media item stuff (which makes sense), in the API spec it is simply ContentScanMetadata. Maybe we could adopt that as well?

[Snipy7374]

With ContentScanMetadata we lose scope, these flags are meaningful only inside UnfurledMediaItem(s) we at least need Unfurled somewhere in the name IMO, e.g: UnfurledContentScanMetadata or UnfurledItemContentScanMetadata

[shiftinv]

these flags are meaningful only inside UnfurledMediaItem(s)

For now, yes, but this could potentially change in the future, we just kinda don't know :/
You're right, though, I suppose ContentScanMetadata is a lil unspecific. Maybe UnfurledMediaScanMetadata/UnfurledMediaScanFlags, then?