[WIP] Experimental: Channel Type Splitting/Abstraction Draft #698
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Analysis:
The existing DiscordChannel class is monolithic (1693 lines) and contains properties/methods for ALL channel types:
Planned Abstraction Hierarchy:
DiscordChannelBase
- Core properties (Id, Name, Type, Position, Flags)DiscordGuildChannelBase
- Guild-specific (GuildId, ParentId, PermissionOverwrites)DiscordTextChannelBase
- Text messaging (Topic, LastMessageId, PerUserRateLimit)DiscordVoiceChannelBase
- Voice functionality (Bitrate, UserLimit, QualityMode)DiscordThreadChannelBase
- Thread functionality (ThreadMetadata, Members)This will be implemented in DisCatSharp.Experimental as an experimental draft for future refactoring.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.