feat(integrations): introduce optional SocialProviderCapabilities con…#1251
Open
benceabel69 wants to merge 1 commit into
Open
feat(integrations): introduce optional SocialProviderCapabilities con…#1251benceabel69 wants to merge 1 commit into
benceabel69 wants to merge 1 commit into
Conversation
|
@benceabel69 is attempting to deploy a commit to the Listinai Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Feature (non-breaking architectural enhancement)
Why was this change needed?
As the number of supported social providers grows, feature support (e.g. threads, polling, analytics, media limits, comments) is currently inferred implicitly through optional methods and scattered flags across provider implementations.
This can lead to:
To address this, this PR introduces a structured and backward-compatible
SocialProviderCapabilitiesinterface and extends the existingSocialProvidercontract with an optionalcapabilitiesproperty.This allows providers to explicitly declare supported features without introducing breaking changes or modifying existing behavior.
This change:
The capability property has been implemented for:
Other providers continue to function unchanged.
Other information:
This change was designed to be minimal and surgical, focusing only on extending the integration abstraction layer without refactoring unrelated code.
The goal is to provide a scalable foundation for future feature introspection (e.g. dynamic UI rendering, validation rules, or provider-specific feature toggling) while maintaining compatibility with all existing providers.
No configuration, infrastructure, or dependency changes were introduced.
Checklist: