-
Notifications
You must be signed in to change notification settings - Fork 29
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
CALL-3878: Migrate to TS and add CJS & ESM Builds #174
base: master
Are you sure you want to change the base?
Conversation
* Create incoming call started method to test inbound calling
* Refactor constants * Refactor version constant * 0.1.6-alpha.0 * Remove sdkVersion prop from initialized event * 0.1.6-alpha.1 * Introduce inbound calling availability events * Test new events * Configure prettier and format the demo-minimal-js html. Improve accessibility and SEO. * Use semantic html and style buttons * Refactor switch case into onclick methods and remove logic that waits for DOM content loaded since we are using defer to load the JS * Rename id * Specify encoding * Match SDK event name * sort props * Initialize as logged out * Add user availability events * Prevent window overflow * Allow user to change availability during a call. * disable availability buttons during a call. * 0.1.7-alpha.0 * Use new alpha version
Create event handlers for create_engagement_succeeded and create_engagement_failed
* Initialize SDK on ready event * Save userAvailable state in the demo widget * Allow user to start an incoming call asynchronously for testing (#146)
* Initialize SDK on ready event * Save userAvailable state in the demo widget * Allow user to start an incoming call asynchronously for testing (#146) * Revert "Allow user to start an incoming call asynchronously for testing (#146)" This reverts commit 9800470. --------- Co-authored-by: Esme Ling <[email protected]> Co-authored-by: Esme <[email protected]>
* Add events for caller id matching * Add caller id match payload * Add debugMessageType argument to logging * Add incomingCall event handler to README * Log last sync event
* Add support for inbound calling to react demo app * Add unit tests for Incoming Screen * Unit tests * Fix useCti hook to store incomingNumber * Feedback fixes # 1 * Feedback fixes #2 * Feedback fixes
* Send navigate_to_record event when we receive an existing call id * Fix console debug message const * Navigate to record page in the react demo app (#165) * Update README with instructions for redirect * 0.2.1-alpha.3 * Use next tag of SDK
…166) * React Demo App: Set incoming number and contact info in localstorage on redirect * feedback fixes
* switch case lost its case to dictionary * Handle NAVIGATE_TO_RECORD_FAILED * Add event handler to demos * Remove unused message handler
|
These changes mean we are coupling our inbound calling release with the TS migration. Here are a few concerns:
|
Yeah these are valid concerns. We could do the following to mitigate risk:
|
I agree we should split this up into multiple PRs and incrementally migrate. I doubt we would need to duplicate files as we are exporting from index.js. So, customers always import from the package which points to index file. Internal structure shouldnt cause problem. I was not aware of realistic date for inbound GA. But, from this PR, we can split up our story into tasks and do incremental migration release. |
Ideally breaking change warrants for major version release. But, our timeline might not be helpful here. |
Description
Jira Ticket: CALL-3878
Merge Checklist
BRAVE Checklist