Problem Definition:
When admins and developers are assigning action overrides to Lightning components it is benifical to only see those that support the object they are relevant to. Allowing them to select any component that implements the lightning:actionSupport interface (regardless of object) can add confusion and force developers to write extra code to mitigate the wrong component being selected.

Suggested Solution:
Unlike Visualforce page overrides that are explicitly linked with their object at development time and only useable with the stated object, your component can actually be assigned to actions on any object. The docs remind you of this fact and offer some best practices.

The sfdc:object qualifier in the .design file is used by developers and Lightning App Builder to filter components to only show up in the design for relevant record pages. This same approach could be used to filter components shown when assigning Lightning Component Bundles.

Salesforce

Need Help?

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.

Merge this idea with:

Optional Comments:

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.

Details:

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.