Fix/salesforce textdecoderstream #4
Merged
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.
This pull request improves compatibility of the Copilot streaming client with Salesforce Lightning environments (Locker/LWS), and updates project dependencies. The main change is to ensure the app gracefully falls back to REST polling when the required streaming API (
TextDecoderStream) is unavailable, preventing runtime errors in restricted environments.Compatibility improvements for Salesforce Lightning (Locker/LWS):
TextDecoderStreambefore enabling the streaming Direct Line client, logging a debug message and falling back to REST polling if unavailable. (lightningCopilotAuth.js)postActivitymethod to only use the streaming client whenTextDecoderStreamis present, ensuring robust handling in environments where this API is missing. (lightningCopilotAuth.js)Dependency updates:
@salesforce/clias a project dependency inpackage.jsonto support Salesforce CLI operations.