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

[Copilot] New IsCapabilityRegisteredSaaS api #1835

Closed
wants to merge 1 commit into from

Conversation

darjoo
Copy link
Contributor

@darjoo darjoo commented Aug 19, 2024

Summary

New api IsCapabilityRegisteredSaaS will check if a capability has been registered and specifically if it is on SaaS environment.

Work Item(s)

Fixes AB#544933

@darjoo darjoo requested a review from a team as a code owner August 19, 2024 18:47
@github-actions github-actions bot added this to the Version 25.0 milestone Aug 19, 2024
@mikebcMSFT
Copy link

Are there downsides to also checking for SaaS rather than cleaner separation of concern and focusing only on registration check?

For example, if our registration system changes in the future (note: no plans to do so), then apps will lose the SaaS check.

/// <param name="CopilotCapability">The capability.</param>
/// <returns>True if the capability has been registered.</returns>
/// <remarks>Capabilities are tied to the module registering it. Checking for a capability will check if the enum and app id of your module exists.</remarks>
procedure IsCapabilityRegisteredSaaS(CopilotCapability: Enum "Copilot Capability"): Boolean
Copy link
Contributor

Choose a reason for hiding this comment

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

Similar to Mike's comment, the purpose of this procedure is to determine if your copilot action should be visible. The actual implementation logic isn't relevant.

Should we rename it to IsCapabilityActionVisible, or something along those lines? Then if the logic changes, we don't need to obsolete.

@darjoo darjoo closed this Aug 20, 2024
@darjoo
Copy link
Contributor Author

darjoo commented Aug 20, 2024

Closed as PR is not needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants