Skip to content

fix(@webex/meetings): only fire aiEnableRequest event if the locus url for the meeting matches the event#4824

Open
dominiccarrington wants to merge 1 commit intowebex:nextfrom
dominiccarrington:docarrin/fix/aiEnableRequest-firing-on-all-meetings
Open

fix(@webex/meetings): only fire aiEnableRequest event if the locus url for the meeting matches the event#4824
dominiccarrington wants to merge 1 commit intowebex:nextfrom
dominiccarrington:docarrin/fix/aiEnableRequest-firing-on-all-meetings

Conversation

@dominiccarrington
Copy link
Copy Markdown
Contributor

This pull request addresses

aiEnableRequest firing for all meetings in the meeting collection

by making the following changes

Checking if the locusUrl in the approval object matches the meeting's locusUrl

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

  • Joining 2 meetings with the same user and requesting AI Assistant to be enabled in one meeting
    • With this bug fix, the event is only recieved in the meeting that sent the request

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

Make sure to have followed the contributing guidelines before submitting.

@dominiccarrington dominiccarrington requested review from a team as code owners April 1, 2026 12:13
@dominiccarrington dominiccarrington added the validated If the pull request is validated for automation. label Apr 1, 2026
@aws-amplify-us-east-2
Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-4824.d3m3l2kee0btzx.amplifyapp.com

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

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants